forked from 0xWheatyz/SPARC
Remove hardcoded database credentials from docker-compose.yml #133
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?
Context
docker-compose.ymlembedspostgres:postgrescredentials in plain text, which will be committed to version control and visible to anyone with repo access.Work
docker-compose.ymlwith environment variable interpolation (e.g.,${POSTGRES_USER},${POSTGRES_PASSWORD})..env.examplefile listing all required variables with safe placeholder values.READMEor developer docs to instruct contributors to copy.env.exampleto.env..envis listed in.gitignore.Acceptance Criteria
docker-compose.ymlcontains no hardcoded credentials.docker compose upworks when a valid.envfile is present..env.exampledocuments every required variable..envis gitignored.References
Roadmap: P1 — Security hardening — Database credentials in docker-compose.yml.
Closing: docker-compose.yml now uses environment variable substitution for all database credentials. Resolved.