feat: staging environment mirroring production (#295)#456
Open
ladinoraa wants to merge 1 commit into
Open
Conversation
- Rewrite deploy-staging.yml: - Triggered on push to develop - CI gate (pnpm test + Redis service) must pass before deploy - Deploys to separate Vercel staging project via VERCEL_PROJECT_ID_STAGING - Health check (5 retries) against /api/health after deploy - Staging Stellar network hardcoded to testnet; production uses mainnet - Expand .env.staging.example with all required variables including REDIS_URL, CORS_ALLOWED_ORIGINS, separate Supabase project values - Add docs/STAGING.md: full setup guide (Vercel project, Supabase project, testnet contract deploy, GitHub secrets, local simulation, smoke test) - Update docs/deployments.md: add staging contract ID table Closes AnnabelJoe#295
|
@ladinoraa Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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.
Summary
Closes #295
Sets up a proper staging environment on Vercel that mirrors production, ensuring changes are validated on testnet before hitting mainnet.
Changes
.github/workflows/deploy-staging.yml— complete rewrite: CI gate (pnpm test + Redis service) → Vercel deploy to separate staging project viaVERCEL_PROJECT_ID_STAGING→ health check (5 retries) → summary URLapps/web/.env.staging.example— expanded with all required vars (Supabase, Stellar testnet, minter key, Redis, CORS, Vercel IDs)docs/STAGING.md(new) — full setup guide: Vercel project, Supabase project, testnet contract deploy, GitHub secrets, Vercel env vars, local simulation, smoke test, promote-to-production flowdocs/deployments.md— staging contract ID table addedAcceptance criteria