alex
dab37a88e8
- Remove env_file references from docker-compose.yml and docker-compose.prod.yml - Add explicit environment variable forwarding for all services - Use TRAEFIK_NETWORK env var in docker-compose.traefik.yml instead of hardcoded name - Add VITE_* frontend variables to .env.example and deploy/.env.example - Add missing production variables (TRAEFIK_ENTRYPOINT, TRAEFIK_CERT_RESOLVER) to deploy/.env.example This makes environment configuration more explicit and easier to manage across different deployment scenarios (local dev, CI/CD, Portainer).
Deploy Skeleton
This directory contains deployment-focused examples and environment templates for the Headquarter platform.
Files
| File | Purpose |
|---|---|
portainer.env.example |
Environment variables for a Portainer-managed stack |
traefik-labels.example.yml |
Reference Traefik labels for services and tool instances |
Assumptions
- An external Traefik reverse proxy is already running on the target Docker host.
- Traefik is attached to a Docker network (default name:
traefik). - The Traefik network is declared as
external: truein compose overlays. - TLS termination and certificate resolution are handled by Traefik.
Usage
- Copy
portainer.env.exampleto your secrets manager or Portainer environment configuration. - Fill in all empty values (client IDs, secrets, database password, encryption key).
- Deploy the stack via Portainer using
docker-compose.yml+docker-compose.traefik.yml. - Tool subdomain labels will be generated dynamically in FN-006.
Traefik Network
Create the Traefik network if it does not exist:
docker network create traefik
Follow-up
Detailed deployment automation, dynamic labels for spawned tool containers, and CI/CD integration are planned in FN-006.