fix: retry production health checks during startup
This commit is contained in:
@@ -81,7 +81,7 @@ The deploy script:
|
||||
4. writes the deployed Git revision to `.deploy-revision`
|
||||
5. builds the Docker image on the VPS
|
||||
6. recreates only the `bmp_website` app container
|
||||
7. verifies `/` and `/admin`
|
||||
7. verifies `/` and `/admin`, retrying transient startup failures for up to 60 seconds
|
||||
|
||||
The required workflow is:
|
||||
|
||||
@@ -114,6 +114,18 @@ If the Caddy container also needs to be recreated:
|
||||
DEPLOY_CADDY=1 pnpm deploy:vps
|
||||
```
|
||||
|
||||
The post-deploy verification tolerates brief `502` responses while Next/Payload
|
||||
starts. Its retry behavior can be adjusted when needed:
|
||||
|
||||
```bash
|
||||
VERIFY_RETRIES=30
|
||||
VERIFY_RETRY_DELAY_SECONDS=2
|
||||
VERIFY_RETRY_MAX_SECONDS=60
|
||||
VERIFY_REQUEST_TIMEOUT_SECONDS=20
|
||||
```
|
||||
|
||||
Set `SKIP_VERIFY=1` only when verification is being performed separately.
|
||||
|
||||
## Payload Migrations
|
||||
|
||||
Routine deploys do not run migrations. For schema-changing commits, create and
|
||||
|
||||
Reference in New Issue
Block a user