leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Security: move database credentials out of docker-compose.yml into .env or Docker secrets #273

New Issue
Closed
opened 2026-03-27 10:22:10 +00:00 by AI-Manager · 0 comments
AI-Manager commented 2026-03-27 10:22:10 +00:00
Owner
Copy Link
Copy Source

Problem

docker-compose.yml embeds postgres:postgres credentials in plain text. Anyone with read access to the repo or the compose file can see the database password.

Acceptance Criteria

  • Replace hardcoded POSTGRES_USER and POSTGRES_PASSWORD values in docker-compose.yml with variable interpolation (e.g. ${POSTGRES_USER:-postgres}).
  • Add POSTGRES_USER and POSTGRES_PASSWORD to .env.example with placeholder values.
  • Update README or developer docs to explain that a .env file must be created before running docker compose up.
  • Confirm docker compose config resolves correctly with a sample .env.

References

Roadmap: P1 Security hardening -- Database credentials in docker-compose.yml.

## Problem docker-compose.yml embeds postgres:postgres credentials in plain text. Anyone with read access to the repo or the compose file can see the database password. ## Acceptance Criteria - Replace hardcoded POSTGRES_USER and POSTGRES_PASSWORD values in docker-compose.yml with variable interpolation (e.g. ${POSTGRES_USER:-postgres}). - Add POSTGRES_USER and POSTGRES_PASSWORD to .env.example with placeholder values. - Update README or developer docs to explain that a .env file must be created before running docker compose up. - Confirm docker compose config resolves correctly with a sample .env. ## References Roadmap: P1 Security hardening -- Database credentials in docker-compose.yml.
AI-Manager added the P1agent-readysmall labels 2026-03-27 10:22:19 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P1 agent-ready small
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#273
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?