rezervovator/deploy/.env.example

# 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

# Reverse proxy in front of the customer containers:
#   traefik  runs as a container of this stack, routes by domain, can issue certificates itself
#   nginx    the nginx already installed on this host. Every customer container listens on
#            127.0.0.1 on its own port (from BASE_PORT up) and the script generates an nginx
#            server block for it. TLS is up to nginx; the settings below REZERVATOR_TLS are ignored.
REZERVATOR_PROXY=traefik
BASE_PORT=3100

# PostgreSQL server holding the customer databases:
#   container  runs as a container of this stack
#   host       the PostgreSQL already installed on this host. The script manages databases
#              with "PG_ADMIN psql" and the containers connect to PG_HOST:PG_PORT.
REZERVATOR_POSTGRES=container
PG_ADMIN="sudo -u postgres"
PG_HOST=host.docker.internal
PG_PORT=5432

# Only for REZERVATOR_PROXY=traefik:
# 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 Traefik
HTTP_PORT=80
HTTPS_PORT=443

# Only for REZERVATOR_POSTGRES=container: password of the PostgreSQL superuser.
# Generated by ./rezervator.sh init.
POSTGRES_PASSWORD=

# Connection limits. max_connections of PostgreSQL must be above
# (number of customers) x CUSTOMER_MAX_CONNECTIONS, or put PgBouncer in front of PostgreSQL.
# PG_MAX_CONNECTIONS sets it for REZERVATOR_POSTGRES=container; on the host, set it in postgresql.conf.
PG_MAX_CONNECTIONS=300
CUSTOMER_MAX_CONNECTIONS=5