No description
--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 |
||
|---|---|---|
| builder | ||
| docs | ||
| infra | ||
| proxy | ||
| scripts | ||
| server | ||
| .dockerignore | ||
| .env.example | ||
| .gitattributes | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| README.md | ||
Be in control of YOUR apps and YOUR data
Features
- Deploy ANY containerized apps in seconds
- Builtin security
- Builtin postgres
- Uses podman for app isolation
- Runs on your hardware (linux vm/host)
- Integrate with git using github webhooks or add your own git remote
- automatic redeployment after git push
- Builtin ssl. Automatically provisioned using let's encrypt.