wmair
4e43a6f713
All image references in docker-compose.yml and docker-compose.local.yml
are replaced with ${IMAGE_VAR:-default} env var syntax, so compose files
work standalone without .env while deploy.sh writes resolved image paths.
deploy.sh gains two new prompts:
- Custom registry prefix (prepended to all image names)
- Hardened images from dhi.io for Redis/PostgreSQL/Caddy (takes priority
over custom registry for those three)
Compared to PR #10: interactive prompts instead of hardcoded vars,
no sed-based compose file mutation, all 14 images covered (PR #10 missed
element-admin, element-call, lk-jwt-service, and all 3 bridges), and
standalone compose usage is preserved via :-default fallbacks.
SETUP.md and README.md document the feature including a note on
pull-through cache registries (Harbor/Artifactory/Nexus) that require
the full docker.io/ path prefix in image names.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Compose File Variants
This folder contains alternative Docker Compose configurations that are not used in the main deployment.
Files
- docker-compose.old.yml - Original compose configuration (legacy)
- docker-compose.local.yml - Local testing configuration with self-signed certificates
- docker-compose.authelia.yml - Standalone Authelia service
- docker-compose.caddy.yml - Standalone Caddy service
Active Configuration
The active configuration is in the root directory as docker-compose.yml (production configuration).
Usage
These variants can be used for:
- Local development and testing (docker-compose.local.yml)
- Reference for different deployment architectures
- Standalone service testing
To use a variant:
docker compose -f compose-variants/docker-compose.local.yml up -d