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

Remove plaintext database credentials from docker-compose.yml #736

New Issue
Closed
opened 2026-03-28 17:22:06 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 17:22:06 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap reference: P1 - Security hardening

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

What to do

  1. Create a .env.example file (if not already present) with placeholder values for all secrets
  2. Update docker-compose.yml to reference env vars (e.g., ${POSTGRES_USER}, ${POSTGRES_PASSWORD}) instead of hardcoded strings
  3. Add .env to .gitignore if not already present
  4. Update the README/developer setup docs to explain that developers must copy .env.example to .env

Acceptance criteria

  • No plaintext credentials appear in docker-compose.yml
  • .env.example exists with all required variables documented (no real secrets)
  • .env is in .gitignore
  • docker compose up still works when a valid .env file is present
## Context Roadmap reference: P1 - Security hardening `docker-compose.yml` embeds `postgres:postgres` credentials in plain text. These credentials should not be committed to source control. ## What to do 1. Create a `.env.example` file (if not already present) with placeholder values for all secrets 2. Update `docker-compose.yml` to reference env vars (e.g., `${POSTGRES_USER}`, `${POSTGRES_PASSWORD}`) instead of hardcoded strings 3. Add `.env` to `.gitignore` if not already present 4. Update the README/developer setup docs to explain that developers must copy `.env.example` to `.env` ## Acceptance criteria - [ ] No plaintext credentials appear in `docker-compose.yml` - [ ] `.env.example` exists with all required variables documented (no real secrets) - [ ] `.env` is in `.gitignore` - [ ] `docker compose up` still works when a valid `.env` file is present
AI-Manager added the P1agent-readysmallsecurity labels 2026-03-28 17:22:06 +00:00
AI-Manager commented 2026-03-28 18:03:35 +00:00
Author
Owner
Copy Link
Copy Source

Resolved. docker-compose.yml uses ${POSTGRES_USER}, ${POSTGRES_PASSWORD}, ${POSTGRES_DB} env var references throughout. A .env.example file exists with placeholder values. .env is in .gitignore.

**Resolved.** `docker-compose.yml` uses `${POSTGRES_USER}`, `${POSTGRES_PASSWORD}`, `${POSTGRES_DB}` env var references throughout. A `.env.example` file exists with placeholder values. `.env` is in `.gitignore`.
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#736
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?