Ilia Denisov
2c465c01d2
CI / changes (pull_request) Successful in 2s
CI / unit (pull_request) Successful in 10s
CI / integration (pull_request) Successful in 18s
CI / ui (pull_request) Successful in 1m4s
CI / conformance (pull_request) Successful in 9s
CI / gate (pull_request) Successful in 0s
CI / deploy (pull_request) Successful in 1m39s
A browser has no signed VK Mini App launch params, so linking VK on the web uses
VK ID's raw OAuth 2.1 flow (PKCE, no @vkid/sdk): the SPA redirects to VK's hosted
login and returns with an authorization code, which the gateway exchanges
server-side (confidential, under the VK "Web" app's protected key) for the trusted
vk user id — then the existing link/merge machinery attaches or merges it.
- fbs LinkVKRequest{code, device_id, code_verifier}; codec + TS bindings.
- backend link.Service ConfirmVK/MergeVK/attachVK (KindVK, mirror Telegram),
handleLinkVK[Merge], routes /user/link/vk[/merge], backendclient LinkVK[Merge].
- gateway internal/vkid confidential code exchange (id.vk.com/oauth2/auth);
transcode link.vk.confirm/merge (registered only when configured) + config
GATEWAY_VK_ID_{APP_ID,CLIENT_SECRET,REDIRECT_URL} + main wiring.
- UI lib/vkid (PKCE authorize redirect + callback), Profile "Link VK" control,
boot callback handling; a merge re-authorizes for a fresh code (VK codes are
single-use). Web-only (a redirect strands a Mini App webview).
- Deploy: VITE_VK_APP_ID + VITE_VK_ID_REDIRECT_URL build args + gateway env,
ci.yaml/prod-deploy TEST_/PROD_ vars, compose/Dockerfile/.env.example/README.
- Tests: vkid exchange unit (string/number user_id, id_token fallback, errors),
transcode link.vk, backend ConfirmVK/MergeVK inttest, codec encodeLinkVK.
- Docs: ARCHITECTURE §4, FUNCTIONAL(+ru), gateway README.
81 lines
3.7 KiB
Docker
81 lines
3.7 KiB
Docker
# Multi-stage build for the gateway service and the landing image. A node stage
|
|
# builds the static UI (Vite) once; the `landing` target serves that build from a
|
|
# static caddy container (the public landing at /, R3), while the final gateway
|
|
# target embeds it — minus landing.html — into the Go binary
|
|
# (gateway/internal/webui/dist), which serves the game SPA at /app/ and
|
|
# /telegram/ (docs/ARCHITECTURE.md §13). The Go stage mirrors
|
|
# platform/telegram/Dockerfile and ships on distroless nonroot.
|
|
#
|
|
# The production UI build vars are image build-args, baked into the bundle.
|
|
# Build from the repository root so go.work, pkg/, gateway/, ui/ and
|
|
# deploy/landing/ are all in the Docker context:
|
|
# docker build -f gateway/Dockerfile \
|
|
# --build-arg VITE_GATEWAY_URL=https://example \
|
|
# -t scrabble-gateway .
|
|
# docker build -f gateway/Dockerfile --target landing -t scrabble-landing .
|
|
|
|
# --- UI build ----------------------------------------------------------------
|
|
FROM node:22-alpine AS ui
|
|
WORKDIR /ui
|
|
RUN corepack enable && corepack prepare pnpm@11.0.9 --activate
|
|
|
|
# Prod UI build vars (Vite reads VITE_-prefixed env at build; baked into the bundle).
|
|
# VITE_APP_VERSION carries `git describe` for the About screen (defaults to "dev").
|
|
ARG VITE_TELEGRAM_BOT_ID=
|
|
ARG VITE_TELEGRAM_LINK=
|
|
ARG VITE_TELEGRAM_GAME_CHANNEL_NAME=
|
|
ARG VITE_VK_APP_LINK=
|
|
ARG VITE_VK_APP_ID=
|
|
ARG VITE_VK_ID_REDIRECT_URL=
|
|
ARG VITE_GATEWAY_URL=
|
|
ARG VITE_APP_VERSION=
|
|
ENV VITE_TELEGRAM_BOT_ID=$VITE_TELEGRAM_BOT_ID \
|
|
VITE_TELEGRAM_LINK=$VITE_TELEGRAM_LINK \
|
|
VITE_TELEGRAM_GAME_CHANNEL_NAME=$VITE_TELEGRAM_GAME_CHANNEL_NAME \
|
|
VITE_VK_APP_LINK=$VITE_VK_APP_LINK \
|
|
VITE_VK_APP_ID=$VITE_VK_APP_ID \
|
|
VITE_VK_ID_REDIRECT_URL=$VITE_VK_ID_REDIRECT_URL \
|
|
VITE_GATEWAY_URL=$VITE_GATEWAY_URL \
|
|
VITE_APP_VERSION=$VITE_APP_VERSION
|
|
|
|
# Install with the lockfile first (the workspace file carries pnpm's build-script
|
|
# approval for esbuild), then build. Committed src/gen/ means no codegen here.
|
|
COPY ui/package.json ui/pnpm-lock.yaml ui/pnpm-workspace.yaml ./
|
|
RUN pnpm install --frozen-lockfile
|
|
COPY ui ./
|
|
RUN pnpm build
|
|
|
|
# --- landing -------------------------------------------------------------------
|
|
# The public landing page as its own static container: the same Vite build
|
|
# served by caddy at /, so stray public traffic is absorbed by static file
|
|
# serving and never reaches the Go edge.
|
|
FROM caddy:2-alpine AS landing
|
|
COPY deploy/landing/Caddyfile /etc/caddy/Caddyfile
|
|
COPY --from=ui /ui/dist /srv
|
|
|
|
# --- Go build ----------------------------------------------------------------
|
|
FROM golang:1.26.3-alpine AS build
|
|
WORKDIR /src
|
|
COPY go.work go.work.sum ./
|
|
COPY pkg ./pkg
|
|
COPY gateway ./gateway
|
|
|
|
# Replace the committed placeholder with the freshly built UI before compiling, so
|
|
# go:embed bakes the real bundle into the binary. The landing shell ships in the
|
|
# landing image, not in the gateway.
|
|
RUN rm -rf gateway/internal/webui/dist
|
|
COPY --from=ui /ui/dist gateway/internal/webui/dist
|
|
RUN rm gateway/internal/webui/dist/landing.html
|
|
|
|
# Reduce the workspace to what the gateway needs: gateway + pkg (loadtest is not in
|
|
# this context; its scrabble/gateway replace targets ./gateway, which is present here).
|
|
RUN go work edit -dropuse=./backend -dropuse=./platform/telegram -dropuse=./loadtest
|
|
# VERSION (the deploy passes the git tag) is stamped into the binary via the linker.
|
|
ARG VERSION=dev
|
|
RUN CGO_ENABLED=0 GOOS=linux go build -trimpath -ldflags "-X scrabble/pkg/version.Version=${VERSION}" -o /out/gateway ./gateway/cmd/gateway
|
|
|
|
# --- runtime -----------------------------------------------------------------
|
|
FROM gcr.io/distroless/static-debian12:nonroot AS gateway
|
|
COPY --from=build /out/gateway /usr/local/bin/gateway
|
|
ENTRYPOINT ["/usr/local/bin/gateway"]
|