GitHub Secrets Setup Guide (Backend CI + Deploy)¶

Add secrets here: - https://github.com/rawrjustin/archety/settings/secrets/actions

This guide covers GitHub Actions secrets only.

Runtime configuration (Supabase, Supermemory, Stripe, domains, etc.) is set in Railway Variables: - docs/RAILWAY_SETUP.md

Required secrets (from `.github/workflows/*.yml`)¶

Secret	Purpose	Used by
`RAILWAY_TOKEN`	Auth for Railway CLI	deploy workflows
`RAILWAY_DEV_SERVICE_ID`	Dev service target	`deploy-dev.yml`
`RAILWAY_PROD_SERVICE_ID`	Prod service target	`deploy-prod.yml`
`OPENAI_API_KEY_DEV`	CI test key	`test-pr.yml`, `deploy-dev.yml`
`OPENAI_API_KEY_PROD`	CI test key	`deploy-prod.yml`
`MEM0_API_KEY_DEV`	CI test key (legacy memory fallback)	`test-pr.yml`
`MEM0_API_KEY_PROD`	CI test key (legacy memory fallback)	`deploy-prod.yml`

Optional: - PERPLEXITY_API_KEY_DEV (workflows fall back to a mock value if omitted)

Token - Create a token at https://railway.app/account/tokens, or run:

railway token

Service IDs - Dev:

railway link --environment development --service archety-backend
railway status

- Prod:

railway link --environment production --service archety-backend
railway status

Use your team’s secret manager or provider dashboard. Do not copy-paste real keys into docs or commit them to the repo.

Create a PR targeting dev → Test Pull Request should pass.
Push to dev → Deploy to Development should deploy (requires RAILWAY_TOKEN + RAILWAY_DEV_SERVICE_ID).

git checkout dev
git commit --allow-empty -m "test: trigger dev deploy"
git push origin dev

Check the Actions tab for the run output.