Deploy Production

Trigger

Merge PR staging → main con CI verde e approval GitHub Environment production.

Promozione immagine

Production usa la stessa immagine validata in staging. Il workflow verifica che l’albero Git di main coincida con staging, quindi promuove il manifest OCI dal tag staging al tag main senza rebuild.

ghcr.io/<org>/ez-factoryos@sha256:<digest>

Procedura automatica (GitHub Actions)

1. Backup pre-deploy
2. Approval manuale (GitHub Environment)
3. Promozione del manifest staging → main
4. Il container configurator esegue bench migrate
5. Health check
6. Rollback automatico su failure

Procedura manuale (server)

docker compose -f deploy/compose/production.yml --env-file deploy/env/.env.production pull
docker compose -f deploy/compose/production.yml --env-file deploy/env/.env.production up -d
docker compose -f deploy/compose/production.yml --env-file deploy/env/.env.production exec backend \
  bash -lc 'cd /home/frappe/frappe-bench && bench --site <site> migrate'
bash scripts/health-check.sh

Rollback

Vedi infrastructure/rollback.md.