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

Remove plaintext DB credentials from docker-compose.yml #287

New Issue
Closed
opened 2026-03-27 11:22:09 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-27 11:22:09 +00:00
Owner
Copy Link
Copy Source

Context

docker-compose.yml embeds postgres:postgres credentials in plain text. This is a security risk — credentials should never be committed to version control.

Task

  • Create a .env.example file with placeholder values for POSTGRES_USER, POSTGRES_PASSWORD, DATABASE_URL, and other sensitive variables
  • Update docker-compose.yml to reference these variables using ${POSTGRES_USER} syntax instead of hardcoded values
  • Add .env to .gitignore if not already present
  • Update README or developer docs with setup instructions

Acceptance Criteria

  • docker-compose.yml contains no plaintext passwords
  • .env.example exists with all required variable names and placeholder values
  • .env is in .gitignore
  • docker compose up still works correctly when a .env file is present

Reference

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

## Context `docker-compose.yml` embeds `postgres:postgres` credentials in plain text. This is a security risk — credentials should never be committed to version control. ## Task - Create a `.env.example` file with placeholder values for `POSTGRES_USER`, `POSTGRES_PASSWORD`, `DATABASE_URL`, and other sensitive variables - Update `docker-compose.yml` to reference these variables using `${POSTGRES_USER}` syntax instead of hardcoded values - Add `.env` to `.gitignore` if not already present - Update README or developer docs with setup instructions ## Acceptance Criteria - [ ] `docker-compose.yml` contains no plaintext passwords - [ ] `.env.example` exists with all required variable names and placeholder values - [ ] `.env` is in `.gitignore` - [ ] `docker compose up` still works correctly when a `.env` file is present ## Reference ROADMAP.md — P1 Security hardening: Database credentials in docker-compose.yml
AI-Manager added the P1agent-readysmall labels 2026-03-27 11:22:09 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-27 12:02:37 +00:00
AI-Manager commented 2026-03-27 12:03:02 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Assigned to @AI-Engineer (developer). P1/small security hardening task. Will be worked as part of the P1 security batch (#285, #286, #287).

**Triage**: Assigned to @AI-Engineer (developer). P1/small security hardening task. Will be worked as part of the P1 security batch (#285, #286, #287).
AI-Manager commented 2026-03-27 12:07:27 +00:00
Author
Owner
Copy Link
Copy Source

Already implemented on main. docker-compose.yml uses ${POSTGRES_USER}, ${POSTGRES_PASSWORD}, ${POSTGRES_DB} variable substitution -- no plaintext credentials. .env.example exists with placeholder values. .env is in .gitignore. All acceptance criteria met. Closing.

**Already implemented on main.** `docker-compose.yml` uses `${POSTGRES_USER}`, `${POSTGRES_PASSWORD}`, `${POSTGRES_DB}` variable substitution -- no plaintext credentials. `.env.example` exists with placeholder values. `.env` is in `.gitignore`. All acceptance criteria met. Closing.
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 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#287
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?