Hotfix: forward OAuth env vars from .env to the app container

[rainxchzed]

Production app boots in a crash loop after #15 merged: validateProductionEnv rejects the deploy because OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET, OAUTH_SERVICE_TOKEN, OAUTH_SERVICE_ALLOWED_HOSTS, and OAUTH_WEB_CALLBACK_URL are missing from the container's environment — even though they exist in /opt/github-store-backend/.env.

Root cause: docker-compose.prod.yml uses an explicit environment: map per-service (not env_file:). ${VAR} substitution at compose-parse-time only inlines variables that are listed in the map. PR #15 added the 5 new env vars to validateProductionEnv + .env.example but not to the prod compose file.

This hotfix:

• Replaces the legacy GITHUB_OAUTH_CLIENT_ID mapping with OAUTH_CLIENT_ID (renamed in Real auth: /v1/oauth/{state,exchange,handoff/{id}} with PKCE-S256, S2S guard, atomic getDel #15)
• Adds the 4 other required OAuth env vars to the app service's environment: block
• Adds the optional OAUTH_CLEANUP_DISABLED kill-switch passthrough (${OAUTH_CLEANUP_DISABLED:-} so an empty .env line is fine)

Dev docker-compose.yml intentionally untouched — APP_ENV != production there, so validateProductionEnv is a no-op and the legacy minimal env config still works for local dev.

Verification

$ docker compose -f docker-compose.prod.yml config | grep -E "OAUTH_"
      OAUTH_CLEANUP_DISABLED: ""
      OAUTH_CLIENT_ID: ""
      OAUTH_CLIENT_SECRET: ""
      OAUTH_SERVICE_ALLOWED_HOSTS: ""
      OAUTH_SERVICE_TOKEN: ""
      OAUTH_WEB_CALLBACK_URL: ""

Empty because the laptop has no .env; on the VPS those slots fill from /opt/github-store-backend/.env.

After this lands and auto-deploy fires, the app boots once the operator restarts the container with --force-recreate (or the deploy workflow does that automatically by virtue of compose detecting the file change).

[greptile-apps]

rainxchzed has reached the 50-review limit for trial accounts. To continue receiving code reviews, upgrade your plan.

[coderabbitai]

Warning

Rate limit exceeded

@rainxchzed has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 37 minutes and 30 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2b9b6323-a693-44e5-b901-0b2e67e50d38

📥 Commits

Reviewing files that changed from the base of the PR and between 8680eb5 and e12d0f3.

📒 Files selected for processing (1)

• docker-compose.prod.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/compose-forward-oauth-env

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}