Three fixes to ensure alembic migrations always run in production:
1. entrypoint.sh: add `exec "$@"` passthrough so `docker compose run
--rm backend alembic upgrade head` actually runs alembic instead of
ignoring args and starting uvicorn.
2. entrypoint.sh: remove `|| echo` fallback on alembic — if migration
fails the container must stop, not silently continue.
3. deploy.yml: start only postgres+redis first, run migration, THEN
start backend. Previously the backend started before migration,
ran with stale schema, and the separate migration step was broken
by the entrypoint bug.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
- Use 'docker compose run --rm backend alembic upgrade head' to run
migration in a throwaway container (doesn't need backend running)
- Restore entrypoint migration fallback (don't block startup)
- Restart backend after migration to pick up schema changes
- Remove --no-cache (too slow, was causing timeouts)
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
- Restructured docker-compose for Nginx Proxy Manager (no custom nginx)
- Added domain wordly.art configuration
- Added Prometheus + Grafana monitoring stack with pre-configured dashboards
- Added PostgreSQL backup script to NAS (daily/weekly/monthly rotation)
- Added alert rules for backend, system, and Docker metrics
- Updated deployment guide for NPM + IONOS DNS homelab setup
- Added marketing plan document
- PDF translator and watermark support
- Enhanced middleware, routes, and translator modules
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
- Update backend Dockerfile with PostgreSQL deps and entrypoint
- Add entrypoint.sh with db/redis wait and auto-migration
- Add /ready endpoint for Kubernetes readiness probe
- Enhance /health endpoint with database and Redis status
- Update k8s deployment with PostgreSQL and Redis services
- Add proper secrets management for database credentials
- Update k8s readiness probe to use /ready endpoint
