Move Caddy proxy behind dev profile

This commit is contained in:
Codex
2026-04-24 08:30:09 -05:00
parent 29bc47da4c
commit f7b86dc417
4 changed files with 5 additions and 2 deletions

View File

@@ -39,6 +39,7 @@
- Added a detached production compose launcher at `scripts/prod-up.sh` so the stack can be started without attaching the terminal to container output.
- Added a Traefik compose override sample at `compose.traefik.yml.sample` for production routing and proxy-network attachment.
- The production launcher now targets only `db`, `backend`, and `frontend`, keeping the dev Caddy proxy out of the production path.
- The Caddy proxy service now runs only under the `dev` compose profile, and `scripts/dev-up.sh` enables that profile automatically.
## Storage Status
- Backend media persists in the `backend-media` named Docker volume.

View File

@@ -27,7 +27,7 @@ WalkUp is a collaborative baseball walk-up song app built as a React PWA with a
8. Open `https://kif.local.ascorrea.com`.
## Dev Logs
- `./scripts/dev-up.sh` starts the stack and appends compose output to `logs/docker-compose.log`.
- `./scripts/dev-up.sh` starts the stack with the `dev` profile and appends compose output to `logs/docker-compose.log`.
- `./scripts/dev-logs.sh` captures current service logs to `logs/docker-services.log`.
- Use those files when you want me to inspect startup failures or runtime errors from the Docker stack.

View File

@@ -50,6 +50,8 @@ services:
command: sh -c "npm ci && npm run dev -- --host 0.0.0.0 --port 5173"
proxy:
profiles:
- dev
image: caddy:2.9-alpine
depends_on:
- backend

View File

@@ -12,4 +12,4 @@ echo "Writing docker compose output to ${LOG_FILE}"
echo "Started at $(date -u +"%Y-%m-%dT%H:%M:%SZ")" >> "${LOG_FILE}"
cd "${ROOT_DIR}"
docker compose up --build "$@" 2>&1 | tee -a "${LOG_FILE}"
docker compose --profile dev up --build "$@" 2>&1 | tee -a "${LOG_FILE}"