Garrett Mills
5b4fa81bc1
Drop the Compose/Caddy example: production runs on Kubernetes, and locally the container only needs a forwarded port and a volume. The README now gives the `docker run` steps and what a Kubernetes deployment needs (one replica, since it's a single SQLite file; a volume at /data; TLS at the ingress). The server only shut down on Ctrl-C, so `docker stop` and pod termination, which send SIGTERM, waited out the grace period and killed it. It now shuts down gracefully on either. Also ignore `.env`, which can hold the OIDC client secret.
22 lines
907 B
Plaintext
22 lines
907 B
Plaintext
# Settings for the mtgc-server container, for `docker run --env-file`. Copy to
|
|
# .env (which git ignores) and fill in. See the README's "Running the sync
|
|
# server" for the full list.
|
|
|
|
# Where users reach the server, exactly as they reach it: through your ingress
|
|
# in production, or the forwarded port locally (http://localhost:8080).
|
|
MTGC_PUBLIC_URL=https://mtgc.example.com
|
|
|
|
# Username/password accounts, managed with `mtgc-server user ...`.
|
|
# Set to false to allow single sign-on only.
|
|
MTGC_LOCAL_AUTH=true
|
|
|
|
# Single sign-on (optional). Register a confidential OIDC client with the
|
|
# redirect URI ${MTGC_PUBLIC_URL}/auth/callback.
|
|
#MTGC_OIDC_ISSUER=https://auth.example.com/application/o/mtgc/
|
|
#MTGC_OIDC_CLIENT_ID=
|
|
#MTGC_OIDC_CLIENT_SECRET=
|
|
#MTGC_OIDC_NAME=Authentik
|
|
#MTGC_OIDC_SCOPES=openid email profile
|
|
# Comma-separated; leave unset to let the provider decide who may sign in.
|
|
#MTGC_ALLOWED_EMAILS=
|