Closes #1067

Summary

Implements per-PR staging environments using Fly.io's API, resolving the staging bottleneck issue discussed in #1067.

Problem

Previously, the Epic Stack used a single shared staging environment (app-name-staging) which created several issues:

• Staging bottleneck: Only one PR could be properly tested at a time
• Unclear test failures: Hard to determine if QA failures were from your PR or conflicting changes
• Serial workflow: Teams couldn't perform parallel quality assurance
• Extra setup: Required creating and maintaining a separate staging app during initial deployment

Solution

Each pull request now gets its own isolated staging environment with:

• Unique Fly app per PR (e.g., app-name-pr-123)
• Automatic provisioning of database, secrets, object storage, and Consul
• Pre-seeded test data for immediate testing
• Automatic cleanup when PRs are closed
• GitHub environment integration with deployment URLs

Changes

CI/CD Pipeline (.github/workflows/deploy.yml):

• Added deploy-staging job using superfly/fly-pr-review-apps@1.5.0
• Staging apps use GitHub environment secrets instead of Fly secrets
• Production deployments only run on pushes to main (removed dev branch)
• Automatic resource provisioning: SQLite volume, Tigris storage, Consul, and secrets
• Doesn't run on forks as pull_request from forks has no secret access.

Database Seeding (prisma/seed.staging.sql, other/litefs.yml):

• Created SQL seed file with test users and notes similar to the seed for local development
• Automatically seeds staging databases on first deployment

Documentation Updates:

• docs/deployment.md: Removed staging app setup, added GitHub CLI instructions
• docs/secrets.md: Updated for GitHub environment secrets
• docs/email.md, docs/monitoring.md: Updated secret commands for new workflow
• docs/database.md: Added staging seed documentation

Benefits

• ✅ Parallel QA: Multiple PRs can be tested simultaneously
• ✅ Isolated testing: Each PR has its own environment without conflicts
• ✅ Simplified setup: No separate staging app to configure during initial deployment
• ✅ Automatic cleanup: Resources freed when PRs close
• ✅ Better reviews: Reviewers get direct links to live preview environments

Test Plan

I tested this in my own deployed fork of the epic stack.

See here the production deploy:
https://github.com/kasperpeulen/epic-stack/deployments/production

And here a PR that creates a staging app on the fly:
kasperpeulen#27

Checklist

• Tests updated
• Docs updated

Screenshots