686aca7060
Without --env-file, docker compose resolved variables from the repo root
(cwd), not from services/<service>/.env where the file actually lives.
This caused ${TAILSCALE_BIND_IP} to expand to empty string, binding
fleet-prometheus on 0.0.0.0:9090 instead of the Tailscale-only IP —
a security hole on the public VPS.
Guard mirrors the existing override-file pattern: only add --env-file
when the file exists, so services without .env continue to work as
before. Flag is injected into COMPOSE_CMD (before the `up` subcommand)
so docker compose sees it as a global option.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| deploy-control-plane.sh | ||
| deploy-frigate.sh | ||
| deploy-host.sh | ||
| deploy-node.sh | ||
| deploy-role.sh | ||
| deploy-stability-agent.sh | ||
| deploy.sh | ||
| orchestrate-deploy.sh | ||
| update-all.sh | ||
| verify-agent-fleet.sh | ||