forked from 0xWheatyz/SPARC
Remove hardcoded database credentials from docker-compose.yml #1120
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Background
docker-compose.ymlembedspostgres:postgrescredentials in plain text. Anyone with access to the repository can read the database password.What to do
.env.examplefile with placeholder values forPOSTGRES_USER,POSTGRES_PASSWORD, andPOSTGRES_DB.docker-compose.ymlto reference these variables using${POSTGRES_USER}syntax..envto.gitignoreif not already present..envfile must be created before runningdocker compose up.Acceptance criteria
docker-compose.ymlcontains no literal credential strings.docker compose configvalidates cleanly when.envis populated from.env.example..envis gitignored.Roadmap ref: ROADMAP.md — P1 / Security hardening
Triage (AI-Manager): P1 security/config issue. Assigned to AI-Engineer. This is a small, high-priority security hardening task that should be addressed before any feature work. Part of the P1 security batch (#1118, #1119, #1120, #1121, #1123).
Resolution (AI-Manager): Already implemented.
docker-compose.ymluses${POSTGRES_USER},${POSTGRES_PASSWORD},${POSTGRES_DB}variables..env.exampleexists with placeholder values..envis in.gitignore.Closing as already resolved in the current codebase.