Standardize .env.example files with complete variables and empty values

Changes:
- Reviewed all docker-compose files to identify required variables
- Updated all .env.example files to include ONLY variables used in their respective compose files
- Changed all placeholder values to empty strings for cleaner configuration
- Fixed variable name inconsistency: DOWNLOADS_DIR -> DOWNLOAD_DIR (to match main .env)
- Removed unnecessary variables that aren't used by the compose files

All .env.example files now:
- Contain only the variables actually used in the stack
- Have empty values instead of example placeholders
- Match the variable names used in docker-compose files

This ensures clean, minimal .env files for each stack without any extraneous variables or confusing placeholder values.
This commit is contained in:
2026-02-10 19:14:53 -05:00
parent 96c7ff39a4
commit f318170d02
18 changed files with 166 additions and 122 deletions

View File

@@ -2,15 +2,26 @@
# These variables are used for productivity and collaboration tools
# Base Configuration
DOMAIN=example.duckdns.org
SERVER_HOSTNAME=myserver
TZ=America/New_York
DOMAIN=
TZ=
# Code Server Configuration
CODE_SERVER_PASSWORD=changeme
# User Configuration
PUID=
PGID=
# Nextcloud Configuration
NEXTCLOUD_DIR=
NEXTCLOUD_ADMIN_USER=
NEXTCLOUD_ADMIN_PASSWORD=
NEXTCLOUD_DB_PASSWORD=
NEXTCLOUD_DB_ROOT_PASSWORD=
# WordPress Configuration
WORDPRESS_DB_PASSWORD=
WORDPRESS_DB_ROOT_PASSWORD=
# Gitea Configuration
GITEA_DB_PASSWORD=
# Jupyter Configuration
JUPYTER_TOKEN=changeme
# Directory Configuration
STACKS_DIR=/opt/stacks
JUPYTER_TOKEN=