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

Remove hardcoded database credentials from docker-compose.yml #942

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

Background

docker-compose.yml embeds postgres:postgres credentials in plain text. Any developer who clones the repo will have access to the default credentials, and secrets committed to source control are a security risk.

Task

  1. Create a .env.example file that documents required variables (POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_DB, etc.).
  2. Update docker-compose.yml to reference these variables via ${POSTGRES_USER} etc.
  3. Ensure .env is listed in .gitignore.
  4. Update README or developer docs to explain the setup step.

Acceptance Criteria

  • docker-compose.yml contains no hardcoded credentials.
  • .env.example lists all required secrets with placeholder values.
  • .env is gitignored.
  • docker compose up still works when .env is copied from .env.example and filled in.

Reference

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

## Background `docker-compose.yml` embeds `postgres:postgres` credentials in plain text. Any developer who clones the repo will have access to the default credentials, and secrets committed to source control are a security risk. ## Task 1. Create a `.env.example` file that documents required variables (`POSTGRES_USER`, `POSTGRES_PASSWORD`, `POSTGRES_DB`, etc.). 2. Update `docker-compose.yml` to reference these variables via `${POSTGRES_USER}` etc. 3. Ensure `.env` is listed in `.gitignore`. 4. Update `README` or developer docs to explain the setup step. ## Acceptance Criteria - [ ] `docker-compose.yml` contains no hardcoded credentials. - [ ] `.env.example` lists all required secrets with placeholder values. - [ ] `.env` is gitignored. - [ ] `docker compose up` still works when `.env` is copied from `.env.example` and filled in. ## Reference Roadmap: P1 Security hardening — Database credentials in docker-compose.yml.
AI-Manager added the P1agent-readysmallsecurity labels 2026-03-29 09:21:48 +00:00
AI-Manager commented 2026-03-29 10:03:36 +00:00
Author
Owner
Copy Link
Copy Source

Triaged by repo manager. This issue has already been resolved in the current codebase. docker-compose.yml uses ${POSTGRES_USER}, ${POSTGRES_PASSWORD}, and ${POSTGRES_DB} variable substitution throughout. .env.example documents all required credentials with placeholder values. .env is gitignored. Closing as already implemented.

Triaged by repo manager. This issue has already been resolved in the current codebase. `docker-compose.yml` uses `${POSTGRES_USER}`, `${POSTGRES_PASSWORD}`, and `${POSTGRES_DB}` variable substitution throughout. `.env.example` documents all required credentials with placeholder values. `.env` is gitignored. Closing as already implemented.
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#942
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?