M6.5: enroll lasuite-docs (recipe #5, multi-service + S3/MinIO) — install verified green
All checks were successful
continuous-integration/drone/push Build is passing
continuous-integration/drone Build is passing

9-service stack (frontend/backend/celery/y-provider/docspec/postgres/redis/minio/nginx) converges
9/9 and serves the SPA; install 2 passed on host. Root-caused a deploy timeout: cold-pulling ~9
large images exceeds abra's default 300s convergence TIMEOUT -> bumped to 900 via EXTRA_ENV (the
generic per-recipe mechanism, no harness surgery). upgrade/backup use a postgres marker (docs/docs)
exercising the pg_backup.sh DB-dump hook; verifying next.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-05-27 06:32:21 +01:00
parent 7558654d98
commit daf67e53b9
4 changed files with 128 additions and 0 deletions

View File

@ -0,0 +1,17 @@
# Per-recipe harness config for lasuite-docs (recipe #5 — multi-service + object-storage/S3).
# Stack: app(frontend) + backend(Django/impress) + celery + y-provider + docspec + db(postgres) +
# redis + minio(S3) + web(nginx). OIDC settings are config-only (validated by `manage.py check`, not
# fetched at boot), so the stack starts healthy with placeholder OIDC; login isn't exercised in CI.
# Many services -> generous timeouts.
HEALTH_PATH = "/"
HEALTH_OK = (200, 301, 302)
DEPLOY_TIMEOUT = 900
HTTP_TIMEOUT = 600
def EXTRA_ENV(domain):
# abra's internal per-deploy convergence timeout (the recipe's TIMEOUT env, default 300s) is too
# short for this 9-service stack on a COLD image cache (~9 large images: impress frontend/backend,
# minio, postgres18, redis, docspec, y-provider). Cold pulls exceed 300s -> "deploy timed out 🟠".
# Bump it so the harness deploy waits long enough; verified the stack converges 9/9 once pulled.
return {"TIMEOUT": "900"}