# Kvitt on the Kvitt Pi (SPEC §10.2, D-125). Copy to .env next to compose.yaml and set HA_HOST; check KVITT_UID and
# KVITT_GID against `id -u` and `id -g` on the Pi. Every key is read by compose.yaml and by nothing else.

# compose.yaml: image names ${KVITT_REGISTRY}/kvitt-server and /kvitt-backup (D-104).
KVITT_REGISTRY=gitea.lan/jacobh2
# compose.yaml: image tag of both services; deploy or roll back = change it, then pull and up -d.
KVITT_TAG=v1.0.0
# compose.yaml: the server's KVITT_PUBLIC_URL=https://<this>, used in invite links and the landing page (D-124).
KVITT_PUBLIC_HOST=kvitt.suorra.duckdns.org
# compose.yaml: the server's KVITT_TRUSTED_PROXY, the Home Assistant Pi's (NPM's) LAN IPv4 address, e.g. 192.168.1.20.
HA_HOST=CHANGE_ME
# compose.yaml: uid both containers run as, `id -u` of the user that owns ~/kvitt on the Pi.
KVITT_UID=1000
# compose.yaml: gid both containers run as, `id -g` of the same user.
KVITT_GID=1000
# compose.yaml: the server's KVITT_EB_APP_ID, the Enable Banking application id for card purchases (SPEC §10.4,
# D-175): the key file's name before .pem. Empty: card features off. The key goes to secrets/cards/enable-banking.pem.
KVITT_EB_APP_ID=
# compose.yaml: the server's KVITT_EB_MEMBER_APP_ID, only for a member's own application (CP-13 fallback); empty: the
# member uses KVITT_EB_APP_ID. Its key goes to secrets/cards/enable-banking-member.pem.
KVITT_EB_MEMBER_APP_ID=
# compose.yaml: the backup's Google Drive folder id (OQ-4).
RCLONE_FOLDER_ID=1jDp1dGE5R3H2DBcXCqIPN1iWzQnPkdlV