developer/scrabble-game
1
1
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Stage 1: backend foundation (Postgres, sessions, accounts, OTel) #1

Merged
developer merged 2 commits from feature/stage-1-backend-foundation into master 2026-06-02 12:00:46 +00:00
Conversation 0 Commits 2 Files Changed 45
+3462 -93
developer commented 2026-06-02 11:55:43 +00:00
Owner
Copy Link
Copy Source

Implements Stage 1 per PLAN.md.

  • internal/postgres: pgx-over-database/sql pool (otelsql), embedded goose migrations into schema backend, committed go-jet code + cmd/jetgen.
  • internal/account: durable accounts + unified telegram/email identities (UUIDv7), find-or-create provisioning.
  • internal/session: opaque 256-bit tokens stored as SHA-256 hash, revoke-only; write-through cache gating /readyz.
  • internal/telemetry: OTel providers (none/stdout) + request-timing middleware; config gains Postgres + OTel env.
  • internal/server: /api/v1 group skeleton + X-User-ID middleware; /readyz checks DB ping + cache.
  • Tests: unit + integration (build tag, testcontainers postgres:17); new integration.yaml workflow.
  • Docs: ARCHITECTURE, TESTING, PLAN, READMEs.

CI: both go-unit and integration workflows green on the branch head. Session/account REST handlers deferred to Stage 6; OTLP/dashboards to Stage 11.

Implements Stage 1 per PLAN.md. - internal/postgres: pgx-over-database/sql pool (otelsql), embedded goose migrations into schema `backend`, committed go-jet code + cmd/jetgen. - internal/account: durable accounts + unified telegram/email identities (UUIDv7), find-or-create provisioning. - internal/session: opaque 256-bit tokens stored as SHA-256 hash, revoke-only; write-through cache gating /readyz. - internal/telemetry: OTel providers (none/stdout) + request-timing middleware; config gains Postgres + OTel env. - internal/server: /api/v1 group skeleton + X-User-ID middleware; /readyz checks DB ping + cache. - Tests: unit + integration (build tag, testcontainers postgres:17); new integration.yaml workflow. - Docs: ARCHITECTURE, TESTING, PLAN, READMEs. CI: both go-unit and integration workflows green on the branch head. Session/account REST handlers deferred to Stage 6; OTLP/dashboards to Stage 11.
developer added 2 commits 2026-06-02 11:55:43 +00:00
Stage 1: backend foundation (Postgres, sessions, accounts, OTel)
Tests · Go / test (push) Successful in 11s
Details
Tests · Integration / integration (push) Successful in 8s
Details
eeaad62b10 
- internal/postgres: pgx-over-database/sql pool (otelsql), embedded goose
  migrations into schema 'backend', committed go-jet code + cmd/jetgen tool.
- internal/account: durable accounts + unified telegram/email identities
  (UUIDv7 keys), find-or-create provisioning with unique-conflict handling.
- internal/session: opaque 256-bit tokens stored as a SHA-256 hash, revoke-only
  (no TTL); write-through cache gating /readyz; store + service.
- internal/telemetry: OTel tracer/meter providers (none/stdout) + request-timing
  middleware; internal/config gains Postgres + OTel env loading.
- internal/server: /api/v1 {public,user,internal,admin} skeleton + X-User-ID
  middleware; /readyz checks DB ping + cache; main wires
  telemetry -> db+migrate -> warm cache -> server.
- Tests: unit + integration (build tag 'integration', testcontainers
  postgres:17) for migrations, accounts, sessions, readyz; new integration.yaml.
- Docs: ARCHITECTURE, TESTING, PLAN refinements, root + backend READMEs.

Session/account REST handlers deferred to Stage 6 (gateway); OTLP + dashboards
to Stage 11.
docs: mark Stage 1 done (CI green)
Tests · Go / test (pull_request) Successful in 4s
Details
Tests · Integration / integration (pull_request) Successful in 6s
Details
ab2e42883a
developer merged commit 7bd461bfc7 into master 2026-06-02 12:00:46 +00:00
developer deleted branch feature/stage-1-backend-foundation 2026-06-02 12:00:46 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
owner (Ilia) developer
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: developer/scrabble-game#1
Delete Branch "feature/stage-1-backend-foundation"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?