The worker and API start in parallel; the API applies migrations on its own startup, so on a fresh deploy the worker hit a missing download_jobs table and crash-looped until migrations landed. The worker now polls for the schema before recovering orphans, and (belt-and-suspenders) the compose files gate it on the API being healthy. Fixes the observed prod restart-loop on the v0.22.0 deploy. |
||
|---|---|---|
| .. | ||
| alembic | ||
| app | ||
| alembic.ini | ||
| Dockerfile | ||
| entrypoint.sh | ||
| log_config.json | ||
| requirements.txt | ||