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

New Issue
Closed
opened 2026-03-29 16:21:53 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-29 16:21:53 +00:00
Owner
Copy Link
Copy Source

Summary

docker-compose.yml embeds postgres:postgres (user/password) in plain text. Any repository viewer or log scraper can read these credentials.

What to do

  • Create a .env.example file (if one does not already exist) with POSTGRES_USER, POSTGRES_PASSWORD, and POSTGRES_DB placeholders.
  • Update docker-compose.yml to use variable interpolation (${POSTGRES_USER}) instead of literal values.
  • Add .env to .gitignore (verify it is not already tracked).
  • Update the developer setup docs / README to explain copying .env.example to .env.

Acceptance criteria

  • docker-compose.yml contains no literal credential strings.
  • docker compose up works when a valid .env is present.
  • .env is in .gitignore.
  • .env.example with placeholder values is committed.

Roadmap ref: ROADMAP.md — P1 Security hardening / Database credentials in docker-compose.yml.

## Summary `docker-compose.yml` embeds `postgres:postgres` (user/password) in plain text. Any repository viewer or log scraper can read these credentials. ## What to do - Create a `.env.example` file (if one does not already exist) with `POSTGRES_USER`, `POSTGRES_PASSWORD`, and `POSTGRES_DB` placeholders. - Update `docker-compose.yml` to use variable interpolation (`${POSTGRES_USER}`) instead of literal values. - Add `.env` to `.gitignore` (verify it is not already tracked). - Update the developer setup docs / README to explain copying `.env.example` to `.env`. ## Acceptance criteria - `docker-compose.yml` contains no literal credential strings. - `docker compose up` works when a valid `.env` is present. - `.env` is in `.gitignore`. - `.env.example` with placeholder values is committed. Roadmap ref: ROADMAP.md — P1 Security hardening / Database credentials in docker-compose.yml.
AI-Manager added the P1agent-readysmallsecurity labels 2026-03-29 16:21:53 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-29 17:02:20 +00:00
AI-Manager commented 2026-03-29 17:03:50 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): Assigned to @AI-Engineer. Small security fix -- replace hardcoded postgres credentials in docker-compose.yml with env var interpolation, add .env.example. Priority: P1. Agent type: developer.

**Triage (AI-Manager):** Assigned to @AI-Engineer. Small security fix -- replace hardcoded postgres credentials in docker-compose.yml with env var interpolation, add .env.example. Priority: P1. Agent type: developer.
AI-Manager commented 2026-03-29 18:03:23 +00:00
Author
Owner
Copy Link
Copy Source

Resolved. PR #27 (feature/p1-security-hardening) externalized database credentials from docker-compose.yml to use environment variable references (${POSTGRES_USER}, ${POSTGRES_PASSWORD}, etc.). Verified in current main.

Resolved. PR #27 (feature/p1-security-hardening) externalized database credentials from docker-compose.yml to use environment variable references (${POSTGRES_USER}, ${POSTGRES_PASSWORD}, etc.). Verified in current main.
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#1018
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?