feat: production-ready deploy (supersedes #14)#15
Merged
Conversation
…nfigs
Consolidates all recent work into one clean commit on top of main:
API (apps/api):
- Postgres adapter (pg-identity-store, pg-session-store) with auto-migration
- Store interfaces are now async
- server.ts: DATABASE_URL toggles between Postgres and in-memory
- Dockerfile (multi-stage, shared package build included)
- 001_initial.sql auto-applied on first boot
Build system:
- package.json: explicit shared-first build order (prevents race)
- packages/shared: emits dist/index.js for Node runtime compatibility
Deploy configs:
- railway.json: Dockerfile-based deploy with /health healthcheck
- apps/claim-web/vercel.json: monorepo build command
- .github/workflows/docker.yml: auto-publish to ghcr.io on main
- .env.example: documented environment variables
Docs:
- README.md: badges, architecture, feature table, deploy buttons
- DEPLOY.md: 5-step guide (Supabase → Railway → Vercel → Chrome Store)
Verified locally:
- npm run build → clean
- npm run typecheck → clean
- docker build + docker run → /health returns {ok:true}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request was generated by @kiro-agent 👻
Comment with /kiro fix to address specific feedback or /kiro all to address everything.
Learn about Kiro autonomous agent
Supersedes #14.
This branch is a single clean commit on top of main with no merge history artifacts and no conflicts. PR #14 can be closed without merging; everything is here.
What's included
API (
apps/api/)pg-identity-store.ts,pg-session-store.ts) with auto-migrationDATABASE_URLenv toggles between Postgres (prod) and in-memory (dev)Dockerfilewith multi-stage build (includes shared package build)migrations/001_initial.sqlapplied on first bootBuild system
package.json: explicit shared-first build order (prevents CI race condition)packages/shared: emitsdist/index.jsfor Node runtimepackages/shared/package.json: propermain/types/exportsfieldsDeploy configs (one-click deploys)
railway.json— Railway reads this, deploys Dockerfile with/healthhealthcheckapps/claim-web/vercel.json— Vercel reads this, knows it's a monorepo.github/workflows/docker.yml— auto-publish Docker image toghcr.ioon push to main.env.example— documented variablesDocs
README.md— badges, architecture diagram, feature table, one-click deploy buttonsDEPLOY.md— 5-step walkthrough: Supabase → Railway → Vercel → Chrome Web StoreVerified locally
How to deploy after merge
Total cost: $0/mo on free tiers. See
DEPLOY.mdfor full walkthrough.DATABASE_URLrailway.json), set 3 env varsvercel.json), setTL_API_BASE