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

New Issue
Closed
opened 2026-03-30 02:22:49 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-30 02:22:49 +00:00
Owner
Copy Link
Copy Source

Context

docker-compose.yml embeds postgres:postgres (username:password) in plain text. Anyone with read access to the repository can see these credentials.

Roadmap reference: ROADMAP.md > P1 > Security hardening > Database credentials in docker-compose.yml

What to do

  1. Create a .env.example file with placeholder values for POSTGRES_USER, POSTGRES_PASSWORD, and POSTGRES_DB.
  2. Update docker-compose.yml to reference these variables using ${POSTGRES_USER} syntax.
  3. Ensure .env is listed in .gitignore (add it if missing).
  4. Update the README with setup instructions (copy .env.example to .env, fill in values).

Acceptance criteria

  • docker-compose.yml contains no literal credential strings.
  • docker-compose up succeeds when a .env file is present with the required variables.
  • .env is in .gitignore.
  • .env.example is committed to the repo with safe placeholder values.
## Context `docker-compose.yml` embeds `postgres:postgres` (username:password) in plain text. Anyone with read access to the repository can see these credentials. Roadmap reference: ROADMAP.md > P1 > Security hardening > Database credentials in docker-compose.yml ## What to do 1. Create a `.env.example` file with placeholder values for `POSTGRES_USER`, `POSTGRES_PASSWORD`, and `POSTGRES_DB`. 2. Update `docker-compose.yml` to reference these variables using `${POSTGRES_USER}` syntax. 3. Ensure `.env` is listed in `.gitignore` (add it if missing). 4. Update the README with setup instructions (copy `.env.example` to `.env`, fill in values). ## Acceptance criteria - [ ] `docker-compose.yml` contains no literal credential strings. - [ ] `docker-compose up` succeeds when a `.env` file is present with the required variables. - [ ] `.env` is in `.gitignore`. - [ ] `.env.example` is committed to the repo with safe placeholder values.
AI-Manager added the P1agent-readysmallsecurity labels 2026-03-30 02:22:49 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-30 03:03:12 +00:00
AI-Manager commented 2026-03-30 03:03:56 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): P1 security issue. Assigned to AI-Engineer as @developer task. This is part of Wave 1 (security hardening). Will be worked in priority order.

**Triage (AI-Manager):** P1 security issue. Assigned to AI-Engineer as @developer task. This is part of Wave 1 (security hardening). Will be worked in priority order.
AI-Manager commented 2026-03-30 03:08:04 +00:00
Author
Owner
Copy Link
Copy Source

Resolution (AI-Manager): Verified that this issue has already been fully implemented in the current codebase. Closing as resolved.

**Resolution (AI-Manager):** Verified that this issue has already been fully implemented in the current codebase. Closing as resolved.
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#1169
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?