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

Replace plain-text database credentials in docker-compose.yml with env file or secrets #1422

New Issue
Closed
opened 2026-03-30 19:23:36 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 19:23:36 +00:00
Owner
Copy Link
Copy Source

Summary

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

What to do

  • Replace all hardcoded POSTGRES_USER / POSTGRES_PASSWORD values with references to a .env file (via env_file: or ${VAR} substitution).
  • Add .env to .gitignore and provide a .env.example with placeholder values.
  • Update any documentation that references the default credentials.

Acceptance criteria

  • docker-compose.yml contains no literal credential values.
  • .env is gitignored; .env.example is committed.
  • docker compose up still works when .env is populated.

References

Roadmap: P1 Security hardening -- database credentials.

## Summary `docker-compose.yml` embeds `postgres:postgres` credentials in plain text. These should never be committed to source control. ## What to do - Replace all hardcoded `POSTGRES_USER` / `POSTGRES_PASSWORD` values with references to a `.env` file (via `env_file:` or `${VAR}` substitution). - Add `.env` to `.gitignore` and provide a `.env.example` with placeholder values. - Update any documentation that references the default credentials. ## Acceptance criteria - [ ] `docker-compose.yml` contains no literal credential values. - [ ] `.env` is gitignored; `.env.example` is committed. - [ ] `docker compose up` still works when `.env` is populated. ## References Roadmap: P1 Security hardening -- database credentials.
AI-Manager added the P1agent-readysmallsecurity labels 2026-03-30 19:23:36 +00:00
AI-Manager commented 2026-03-30 20:03:24 +00:00
Author
Owner
Copy Link
Copy Source

Already implemented. docker-compose.yml uses ${POSTGRES_USER}, ${POSTGRES_PASSWORD}, and ${POSTGRES_DB} variable substitution throughout -- no hardcoded credentials. .env is in .gitignore and .env.example provides placeholder values.

Closing as completed.

Already implemented. `docker-compose.yml` uses `${POSTGRES_USER}`, `${POSTGRES_PASSWORD}`, and `${POSTGRES_DB}` variable substitution throughout -- no hardcoded credentials. `.env` is in `.gitignore` and `.env.example` provides placeholder values. 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#1422
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?