Scheduler container needs to reach momo-db (on momo-pro_default network).
Without this, psycopg2 fails with DNS name resolution error on every recreate.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Compose env section was overriding the .env file fix with the wrong hostname,
causing psycopg2 name resolution failure after scheduler recreated via compose.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
CD was failing with 'No such container: momo-telegram-bot' because
the Gitea Actions restart step still listed all three containers.
Changes:
1. .gitea/workflows/cd.yaml:
- Sync mode: docker restart now only targets momo-pro-system momo-scheduler
- Rebuild mode: docker compose up no longer includes telegram-bot service
2. docker-compose.yml:
- Removed telegram-bot service block (38 lines)
- Syncs local repo with remote server state (already removed there)
