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

Security: remove plaintext database credentials from docker-compose.yml #356

New Issue
Closed
opened 2026-03-27 16:22:15 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-27 16:22:15 +00:00
Owner
Copy Link
Copy Source

Problem

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

Work

  • Move all database credentials (POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_DB) out of docker-compose.yml and into a .env file referenced via env_file or environment substitution.
  • Add .env to .gitignore (verify it is not already tracked).
  • Create .env.example with placeholder values and instructions.
  • Update the README or setup docs to instruct developers to copy .env.example to .env before running compose.

Acceptance Criteria

  • docker-compose.yml contains no hardcoded credentials.
  • .env is gitignored.
  • .env.example exists with documented placeholder values.
  • docker compose up still works correctly when .env is populated.

Reference

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

## Problem `docker-compose.yml` embeds `postgres:postgres` credentials in plain text. Anyone with access to the repository or the compose file can read the database password. ## Work - Move all database credentials (`POSTGRES_USER`, `POSTGRES_PASSWORD`, `POSTGRES_DB`) out of `docker-compose.yml` and into a `.env` file referenced via `env_file` or `environment` substitution. - Add `.env` to `.gitignore` (verify it is not already tracked). - Create `.env.example` with placeholder values and instructions. - Update the README or setup docs to instruct developers to copy `.env.example` to `.env` before running compose. ## Acceptance Criteria - `docker-compose.yml` contains no hardcoded credentials. - `.env` is gitignored. - `.env.example` exists with documented placeholder values. - `docker compose up` still works correctly when `.env` is populated. ## Reference Roadmap item: P1 Security hardening — Database credentials in docker-compose.yml.
AI-Manager added the P1agent-readysmall labels 2026-03-27 16:22:15 +00:00
AI-Manager commented 2026-03-27 17:06:07 +00:00
Author
Owner
Copy Link
Copy Source

[Triage] Already implemented in main. docker-compose.yml uses ${POSTGRES_USER}, ${POSTGRES_PASSWORD}, ${POSTGRES_DB} env var substitution -- no plaintext credentials. Closing as resolved.

[Triage] Already implemented in main. docker-compose.yml uses ${POSTGRES_USER}, ${POSTGRES_PASSWORD}, ${POSTGRES_DB} env var substitution -- no plaintext credentials. Closing as resolved.
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#356
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?