mirror of
https://github.com/tiennm99/composes.git
synced 2026-10-04 20:13:20 +00:00
environment: blocks were in no particular order. They now run must-have -> should-have -> optional, with related variables kept adjacent as a group that takes the tier of its most important member: PUID/PGID, PASSWORD with SUDO_PASSWORD, DOCKER_MODS ahead of the INSTALL_PACKAGES and NODEJS_MOD_VERSION that configure it, the four GIT_* entries, the PASEO_* daemon settings. Each .env.example is reordered to match its compose file. The names do not map one to one -- PASSWORD feeds both PASSWORD and SUDO_PASSWORD, SERVICE_HOSTNAME feeds HOST -- so an entry sits where the first compose entry reading it sits. The HOST comment in both compose files is dropped; the READMEs already carry that explanation in full. CLAUDE.md records the ordering convention. alloy and gitea-mirror-local are untouched: every variable there is required, so the tiers collapse and the existing grouping is the better one.
18 lines
585 B
Bash
18 lines
585 B
Bash
# Copy to .env and fill in. Never commit .env.
|
|
#
|
|
# cp .env.example .env
|
|
|
|
# Web UI login password. MUST NOT be blank -- the LinuxServer image serves
|
|
# code-server without authentication when PASSWORD is empty.
|
|
# Also used for SUDO_PASSWORD inside the container.
|
|
# Generate one with: openssl rand -base64 24
|
|
PASSWORD=
|
|
|
|
# Git identity baked into the container (author + committer).
|
|
GIT_NAME=
|
|
GIT_EMAIL=
|
|
|
|
# Container hostname, also passed in as HOST -- the name zsh's prompt shows.
|
|
# Not named HOSTNAME: the deploying shell's own HOSTNAME would override it.
|
|
SERVICE_HOSTNAME=code-server
|