Development and Deployment

Branching Workflow for Fastify Server

1. Main Branches

• main → production code only.
• staging → integration/testing before production.

---

2. Feature Workflow

1. Start from staging for new work:

git checkout staging
git pull origin staging
git checkout -b feature/your-feature

2. Do your work on feature/your-feature.

3. Open a PR into staging.

   • Staging gets deployed to your staging server automatically (CI/CD).
   • QA/testing happens here.

---

3. Promotion to Production

1. When staging is stable:

git checkout main
git pull origin main
git merge staging
git push origin main

2. main is then deployed to production.

---

4. Hotfixes

If production is broken:

1. Branch from main:

git checkout main
git pull origin main
git checkout -b hotfix/urgent-fix

2. Fix → PR into main.
3. After merging, also merge into staging to keep them in sync.

---

5. Environment Mapping

• Dev branches → local testing (http://localhost:3000).
• Staging branch → deployed staging server (https://staging.gigmanager.com).
• Main branch → production server (https://gigmanager.com).

---

6. Automation (CI/CD)

Use CI/CD (GitHub Actions, GitLab CI, etc.):

• Push/merge to staging → auto-deploy staging server.
• Push/merge to main → auto-deploy production.

---

Summary:

• Developers experiment in isolated branches.
• Staging always reflects “next release candidate.”
• Main always reflects “live production.”