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

Security: Remove hardcoded database credentials from docker-compose.yml #711

New Issue
Closed
opened 2026-03-28 16:21:53 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 16:21:53 +00:00
Owner
Copy Link
Copy Source

Summary

docker-compose.yml embeds postgres:postgres (user and password) in plain text. These credentials are visible to anyone with repo access and are a security risk.

What to do

  • Create a .env.example file (if one does not exist) with placeholder values for POSTGRES_USER and POSTGRES_PASSWORD.
  • Update docker-compose.yml to reference ${POSTGRES_USER} and ${POSTGRES_PASSWORD} instead of hardcoded values.
  • Add .env to .gitignore to prevent accidental credential commits.
  • Document the setup step in the README.

Acceptance Criteria

  • docker-compose.yml contains no hardcoded database credentials.
  • .env.example provides template values for all required secrets.
  • .env is listed in .gitignore.
  • docker-compose up works correctly when a valid .env is present.

Reference

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

## Summary `docker-compose.yml` embeds `postgres:postgres` (user and password) in plain text. These credentials are visible to anyone with repo access and are a security risk. ## What to do - Create a `.env.example` file (if one does not exist) with placeholder values for `POSTGRES_USER` and `POSTGRES_PASSWORD`. - Update `docker-compose.yml` to reference `${POSTGRES_USER}` and `${POSTGRES_PASSWORD}` instead of hardcoded values. - Add `.env` to `.gitignore` to prevent accidental credential commits. - Document the setup step in the README. ## Acceptance Criteria - [ ] `docker-compose.yml` contains no hardcoded database credentials. - [ ] `.env.example` provides template values for all required secrets. - [ ] `.env` is listed in `.gitignore`. - [ ] `docker-compose up` works correctly when a valid `.env` is present. ## Reference Roadmap: P1 Security hardening — Database credentials in docker-compose.yml.
AI-Manager added the P1agent-readysmallsecurity labels 2026-03-28 16:21:53 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-28 17:03:01 +00:00
AI-Manager commented 2026-03-28 17:06:28 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] Already resolved. docker-compose.yml uses env var references. .env.example has placeholders. .env is in .gitignore.

Closing as already implemented in the codebase.

[Repo Manager] Already resolved. docker-compose.yml uses env var references. .env.example has placeholders. .env is in .gitignore. Closing as already implemented in the codebase.
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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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