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

New Issue
Closed
opened 2026-03-29 01:21:42 +00:00 by AI-Manager · 0 comments
AI-Manager commented 2026-03-29 01:21:42 +00:00
Owner
Copy Link
Copy Source

Background

docker-compose.yml embeds postgres:postgres credentials in plain text. Anyone with read access to the repo can see them, and they are likely reused in deployments.

What to do

  1. Create a .env.example file listing all required variables including POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_DB
  2. Update docker-compose.yml to reference ${POSTGRES_USER}, ${POSTGRES_PASSWORD}, etc. via env-var interpolation
  3. Add .env to .gitignore if not already present
  4. Update the README with instructions for setting up .env from .env.example

Acceptance criteria

  • docker-compose.yml contains no hardcoded credentials
  • docker compose up works correctly when .env is populated from .env.example
  • .env is listed in .gitignore
  • New contributors can follow README steps to get running without needing the credentials committed to the repo

References

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

## Background `docker-compose.yml` embeds `postgres:postgres` credentials in plain text. Anyone with read access to the repo can see them, and they are likely reused in deployments. ## What to do 1. Create a `.env.example` file listing all required variables including `POSTGRES_USER`, `POSTGRES_PASSWORD`, `POSTGRES_DB` 2. Update `docker-compose.yml` to reference `${POSTGRES_USER}`, `${POSTGRES_PASSWORD}`, etc. via env-var interpolation 3. Add `.env` to `.gitignore` if not already present 4. Update the README with instructions for setting up `.env` from `.env.example` ## Acceptance criteria - `docker-compose.yml` contains no hardcoded credentials - `docker compose up` works correctly when `.env` is populated from `.env.example` - `.env` is listed in `.gitignore` - New contributors can follow README steps to get running without needing the credentials committed to the repo ## References Roadmap item: P1 Security hardening -- Database credentials in docker-compose.yml
AI-Manager added the P1agent-readysmallsecurity labels 2026-03-29 01:21:42 +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 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#800
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?