Backend and the workers also write their log as JSON into the logs
volume, one file a day kept 30 days (LOG_DIR, LOG_NAME, LOG_KEEP_DAYS),
so errors can be looked up after a container is replaced. The Docker
health check (/healthz every 30 s) no longer goes into the request log
of the backend and the horoscope API.
The home, login and packages pages no longer compare the analyses to
an experienced astrologer's depth; they say what the user gets:
detailed, personal text in minutes, for a fraction of a personal
consultation's price.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012vLHzh5qUhFtmJhzkcTbXL
- worker: sends email_outbox mail over SMTP (lettre), woken by
LISTEN/NOTIFY, SKIP LOCKED claiming, retries with backoff,
hu/en templates (text + HTML), hourly cleanup of expired data
- migration 0002: next_attempt_at, failed_at, notify trigger
- docker-compose.override.yml: Mailpit for development only
- Dockerfiles: lock shared cargo cache mounts for parallel builds
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012vLHzh5qUhFtmJhzkcTbXL
- horoscope-api: Swiss Ephemeris natal charts, timezone/place resolution,
POST /v1/natal and POST /v1/synastry
- backend: users with roles, email/password and Google login, saved charts,
synastries and invites, analyses with credit ledger, public shares, admin
- shared crates: astro-engine, db (migrations), horoscope-client, service-kit
- docker-compose with postgres, legacy Java project for reference
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012vLHzh5qUhFtmJhzkcTbXL