ITsolved/rezervovator
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Added health check and deployment setup for one container per customer. Fixes #12

Browse Source 
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
pepa
2026-10-12 16:34:40 +02:00
co-authored by Claude Opus 5.5
parent c1d998878a
commit 156fe1a0f4
14 changed files with 799 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+8
View File
@@ -58,6 +58,14 @@ Set `bind_ip = '0.0.0.0'` in the config so the server is reachable from outside
Older versions of the image expected the config in `/app/target/site/data/config.toml`, where it could be downloaded from `/data/config.toml`. If you ran such a container, move the file and change the database password, the SMTP password and the session key.
## Health check
`GET /health` returns 200 when the server can reach its database and 503 otherwise. `rezervator --healthcheck` asks the running server on this machine and exits with 0 or 1; the Docker image uses it as its health check.
## Hosting many customers
The application serves one company per instance. `deploy/` contains a Docker Compose setup and a script for running one container per customer behind a reverse proxy, including upgrades, backups and restores. See [deploy/README.md](deploy/README.md).
## Running tests
`cargo test --features ssr`