Ivo Oskamp
d98239ddde
Remove the onboarding vars from the committed .env. The compose still passes
them through as ${VAR:-} (optional), so onboarding stays configurable via
Portainer without cluttering .env or warning on deploy.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
27 lines
995 B
Bash
27 lines
995 B
Bash
# Clearview stack environment.
|
|
#
|
|
# All per-deployment values live here. The compose references them with
|
|
# ${VAR:?...}, so the stack refuses to start when a required value is missing —
|
|
# there are no silent defaults. The only thing pinned in the compose itself is
|
|
# the Postgres image version (postgres:16-alpine), because the app's migrations
|
|
# depend on it.
|
|
#
|
|
# This is the dev baseline. For the prod stack, override CLEARVIEW_IMAGE_TAG
|
|
# (latest), CLEARVIEW_ENV (prod) and the host ports in Portainer's stack
|
|
# environment. CLEARVIEW_ENV drives the container names (clearview-<env>, …) and
|
|
# the Postgres data dir (/docker/appdata/clearview-<env>/postgres) so dev and
|
|
# prod run side by side.
|
|
|
|
CLEARVIEW_IMAGE_TAG=dev
|
|
CLEARVIEW_ENV=dev
|
|
CLEARVIEW_PORT=8080
|
|
ADMINER_PORT=8081
|
|
TZ=Europe/Amsterdam
|
|
|
|
POSTGRES_HOST=postgres
|
|
POSTGRES_PORT=5432
|
|
POSTGRES_DB=clearview
|
|
POSTGRES_USER=clearview
|
|
# No default — set this in Portainer's stack environment, or the stack won't start.
|
|
POSTGRES_PASSWORD=
|