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 #877

New Issue
Closed
opened 2026-03-29 05:21:43 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-29 05:21:43 +00:00
Owner
Copy Link
Copy Source

Context

docker-compose.yml embeds postgres:postgres credentials in plain text. These should never be committed to version control.

Roadmap reference: P1 Security hardening

What to do

  1. Create a .env.example file with placeholder values for POSTGRES_USER, POSTGRES_PASSWORD, and POSTGRES_DB.
  2. Update docker-compose.yml to reference these variables using ${POSTGRES_USER} syntax.
  3. Ensure .env is listed in .gitignore.
  4. Update README with setup instructions (copy .env.example to .env and fill in values).

Acceptance criteria

  • No plaintext credentials in docker-compose.yml.
  • .env is gitignored.
  • .env.example documents all required variables.
  • docker compose up still works when .env is present.
## Context `docker-compose.yml` embeds `postgres:postgres` credentials in plain text. These should never be committed to version control. Roadmap reference: P1 Security hardening ## What to do 1. Create a `.env.example` file with placeholder values for `POSTGRES_USER`, `POSTGRES_PASSWORD`, and `POSTGRES_DB`. 2. Update `docker-compose.yml` to reference these variables using `${POSTGRES_USER}` syntax. 3. Ensure `.env` is listed in `.gitignore`. 4. Update README with setup instructions (copy `.env.example` to `.env` and fill in values). ## Acceptance criteria - No plaintext credentials in `docker-compose.yml`. - `.env` is gitignored. - `.env.example` documents all required variables. - `docker compose up` still works when `.env` is present.
AI-Manager added the P1agent-readysmallsecurity labels 2026-03-29 05:21:43 +00:00
AI-Manager commented 2026-03-29 06:03:19 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved. The changes are already merged into main.

docker-compose.yml now uses ${POSTGRES_USER}, ${POSTGRES_PASSWORD}, ${POSTGRES_DB} variables. .env.example documents all required variables.

Closing as completed.

This issue has been resolved. The changes are already merged into main. docker-compose.yml now uses ${POSTGRES_USER}, ${POSTGRES_PASSWORD}, ${POSTGRES_DB} variables. .env.example documents all required variables. Closing as completed.
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 security 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#877
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?