This commit is contained in:
+6
-5
@@ -67,10 +67,10 @@ uses `IMAGE_TAG` to select matching API, worker, and web images. Deploy with:
|
||||
RELEASE_TAG=2026-09-09-01 ./scripts/deploy-production.sh
|
||||
```
|
||||
|
||||
The deploy script builds the three tagged images, starts healthy data services,
|
||||
applies migrations with the tagged API image, and then switches the application
|
||||
services. Keep the previous release tag and migration state with the deployment
|
||||
record.
|
||||
The deploy script builds the three tagged images, waits for healthy data
|
||||
services, applies migrations with the tagged API image, and then switches the
|
||||
application services after they are healthy. Keep the previous release tag and
|
||||
migration state with the deployment record.
|
||||
|
||||
Rollback application images with:
|
||||
|
||||
@@ -78,7 +78,8 @@ Rollback application images with:
|
||||
RELEASE_TAG=2026-09-08-02 ./scripts/rollback-production.sh
|
||||
```
|
||||
|
||||
Image rollback is safe only when the previous image understands the current
|
||||
The rollback script waits for the restored application services to become
|
||||
healthy before running the smoke check. Image rollback is safe only when the previous image understands the current
|
||||
database schema. If the release included an incompatible schema change, restore
|
||||
the matching PostgreSQL backup before starting the previous images. Always
|
||||
verify the API and web health checks after a rollback.
|
||||
|
||||
Reference in New Issue
Block a user