9ba81bd809
--resume caused Caddyfile changes (e.g. new Forgejo block) to be silently ignored on restart because Caddy preferred its saved in-memory config. Instead, Caddy now always starts clean from the Caddyfile, and the HIY server re-registers every app's Caddy route from the DB on startup (restore_caddy_routes). This gives us the best of both worlds: - Caddyfile changes (static services, TLS config) are always picked up - App routes are restored automatically without needing a redeploy https://claude.ai/code/session_01FKCW3FDjNFj6jve4niMFXH |
||
|---|---|---|
| .. | ||
| postgres-init | ||
| .env.example | ||
| backup.sh | ||
| boot.sh | ||
| docker-compose.yml | ||
| Dockerfile.server | ||
| gatus.yml | ||
| Makefile | ||
| start.sh | ||