-
Notifications
You must be signed in to change notification settings - Fork 0
Deployment
anton3x edited this page Nov 15, 2025
·
2 revisions
| Branch | Environment | Purpose |
|---|---|---|
main |
Staging | Used for integration and internal testing. Each push or merged PR triggers automatic deployment to the staging environment. |
production |
Production | Contains stable, production-ready code. Tagged versions (v*) trigger a production deployment and create a GitHub Release. |
| Environment | URL |
|---|---|
| Staging | https://matchby-d4eweaajaffthmh6.italynorth-01.azurewebsites.net |
| Production | https://matchby.me/ |
Every push or merge into main runs:
- Build & test (CI)
- Deployment to the Azure App Service – Staging slot
The production branch is always stable.
When a version tag (e.g., v1.2.0) is created on production:
- CI builds and tests the code again
- CD deploys it to Azure App Service – Production slot
- A GitHub Release is automatically generated with release notes and the build artifact
| Component | Technology |
|---|---|
| CI/CD Platform | GitHub Actions |
| Hosting | Azure App Service |
| Database | PostgreSQL (Supabase) |
| File Storage | AWS S3 (via Supabase Storage) |
- Home - Main documentation index
- Architecture - System architecture
- Sprint Reviews - Deployment history