091583b3dd
Some checks failed
Veza CI / Rust (Stream Server) (push) Successful in 6m16s
Security Scan / Secret Scanning (gitleaks) (push) Successful in 3m0s
Veza CI / Backend (Go) (push) Failing after 16m10s
Veza CI / Frontend (Web) (push) Successful in 23m35s
Veza CI / Notify on failure (push) Successful in 7s
Audit cross-checked against active composes shows three dormant compose
files that duplicate functionality already covered by the canonical
docker-compose.{,dev,prod,staging,test}.yml at the repo root. None are
referenced from Make targets, scripts, or CI workflows. They have
diverged from the active set (different ports, older Postgres version,
no shared volume names, etc.) and are a footgun for new contributors.
Files marked DEPRECATED with a header pointing at the canonical compose
to use instead:
veza-stream-server/docker-compose.yml
Standalone stream-server compose. Same service is provided by the
root docker-compose.yml under the `docker-dev` profile.
infra/docker-compose.lab.yml
Lab Postgres on default port 5432. Conflicts with a host Postgres on
most setups; root docker-compose.dev.yml uses non-default ports for
a reason.
config/docker/docker-compose.local.yml
Local Postgres 15 variant on port 5433. Redundant with root
docker-compose.dev.yml (Postgres 16, project-wide port mapping).
Not in this commit (intentionally limited J6 scope, per audit plan
"verify, don't refactor"):
- No `extends:` consolidation across the active composes — that is a
1-2 day refactor on its own and not a v1.0.4 concern.
- The five active composes were syntactically validated locally
(docker compose config); production and staging both require
operator-injected env vars (DB_PASS, S3_*, RABBITMQ_PASS, etc.)
which is the intended behavior, not a bug.
- Cross-compose audit confirms zero references to the removed
chat-server or any other dead service / image. Only one residual
deprecation warning across all active composes: the obsolete
`version:` field on docker-compose.{prod,test,test}.yml — cosmetic,
not blocking.
- Test suite verification (Go / Rust / Vitest) deferred to Forgejo CI
rather than re-running locally. The pre-push hook + remote pipeline
will gate the next push.
Follow-up candidates (not blocking v1.0.4):
- Delete the three deprecated files once a 2-month grace period
confirms no local dev workflow references them.
- Drop the obsolete `version:` field across the active composes.
Refs: AUDIT_REPORT.md §6.1, §10 P7
79 lines
2.3 KiB
YAML
79 lines
2.3 KiB
YAML
# ============================================================================
|
|
# DEPRECATED — lab environment compose, dormant since February 2026.
|
|
# Overlaps with docker-compose.dev.yml at the repo root (which uses non-default
|
|
# ports to avoid conflicts with a host Postgres). Use docker-compose.dev.yml
|
|
# for day-to-day dev:
|
|
# docker compose -f docker-compose.dev.yml up -d
|
|
# Marked in v1.0.4 cleanup. Candidate for deletion once confirmed unused.
|
|
# ============================================================================
|
|
version: "3.9"
|
|
|
|
services:
|
|
postgres:
|
|
image: postgres:16
|
|
container_name: veza-lab-postgres
|
|
environment:
|
|
POSTGRES_USER: veza
|
|
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-devpassword}
|
|
POSTGRES_DB: veza_lab
|
|
ports:
|
|
- "5432:5432"
|
|
volumes:
|
|
- postgres_lab_data:/var/lib/postgresql/data
|
|
healthcheck:
|
|
test: ["CMD-SHELL", "pg_isready -U veza -d veza_lab"]
|
|
interval: 5s
|
|
timeout: 3s
|
|
retries: 10
|
|
networks:
|
|
- veza-lab-net
|
|
|
|
redis:
|
|
image: redis:7
|
|
container_name: veza-lab-redis
|
|
ports:
|
|
- "6379:6379"
|
|
healthcheck:
|
|
test: ["CMD", "redis-cli", "ping"]
|
|
interval: 5s
|
|
timeout: 3s
|
|
retries: 5
|
|
networks:
|
|
- veza-lab-net
|
|
|
|
rabbitmq:
|
|
image: rabbitmq:3-management
|
|
container_name: veza-lab-rabbitmq
|
|
ports:
|
|
- "5672:5672"
|
|
- "15672:15672"
|
|
environment:
|
|
RABBITMQ_DEFAULT_USER: veza
|
|
RABBITMQ_DEFAULT_PASS: ${RABBITMQ_DEFAULT_PASS:-devpassword}
|
|
healthcheck:
|
|
test: ["CMD", "rabbitmq-diagnostics", "-q", "ping"]
|
|
interval: 10s
|
|
timeout: 5s
|
|
retries: 5
|
|
networks:
|
|
- veza-lab-net
|
|
|
|
haproxy:
|
|
image: haproxy:lts-alpine
|
|
container_name: veza-lab-haproxy
|
|
ports:
|
|
- "80:80"
|
|
# - "443:443" # SSL disabled for now
|
|
volumes:
|
|
- ../docker/haproxy/haproxy.lab.cfg:/usr/local/etc/haproxy/haproxy.cfg:ro
|
|
extra_hosts:
|
|
- "host.docker.internal:host-gateway"
|
|
networks:
|
|
- veza-lab-net
|
|
|
|
volumes:
|
|
postgres_lab_data:
|
|
|
|
networks:
|
|
veza-lab-net:
|
|
driver: bridge
|