Added health check and deployment setup for one container per customer. Fixes #12
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
@@ -0,0 +1,25 @@
|
||||
# Settings of the stack. Copy to .env (./rezervator.sh init does it and generates the password).
|
||||
|
||||
# Prefix of container, network and volume names. Change it to run a second stack on the same host.
|
||||
REZERVATOR_PREFIX=rezervator
|
||||
|
||||
# Image the customer containers are started from
|
||||
REZERVATOR_IMAGE=rezervator:latest
|
||||
|
||||
# true: HTTPS with Let's Encrypt certificates, HTTP is redirected. Needs public DNS records
|
||||
# pointing to this host and ACME_EMAIL.
|
||||
# false: plain HTTP only, for local testing or behind another TLS terminating proxy.
|
||||
REZERVATOR_TLS=true
|
||||
ACME_EMAIL=
|
||||
|
||||
# Ports published by the proxy
|
||||
HTTP_PORT=80
|
||||
HTTPS_PORT=443
|
||||
|
||||
# Password of the PostgreSQL superuser. Generated by ./rezervator.sh init.
|
||||
POSTGRES_PASSWORD=
|
||||
|
||||
# Connection limits. PG_MAX_CONNECTIONS must be above
|
||||
# (number of customers) x CUSTOMER_MAX_CONNECTIONS, or put PgBouncer in front of PostgreSQL.
|
||||
PG_MAX_CONNECTIONS=300
|
||||
CUSTOMER_MAX_CONNECTIONS=5
|
||||
Reference in New Issue
Block a user