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

Move database credentials out of docker-compose.yml into .env file #544

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

Summary

docker-compose.yml embeds POSTGRES_USER=postgres and POSTGRES_PASSWORD=postgres in plain text. This is a security risk and makes credential rotation difficult.

What to do

  • Create a .env.example file (if it does not already exist) with placeholder values for POSTGRES_USER, POSTGRES_PASSWORD, and POSTGRES_DB.
  • Update docker-compose.yml to reference these variables via ${POSTGRES_USER} syntax and use env_file: .env.
  • Add .env to .gitignore.
  • Update README with instructions for copying .env.example to .env before running.

Acceptance Criteria

  • docker-compose.yml contains no hardcoded credential strings.
  • docker compose up works correctly when a .env file is present.
  • .env is listed in .gitignore.
  • .env.example is committed with safe placeholder values.

Reference

Roadmap item: P1 - Security hardening > Database credentials in docker-compose.yml

## Summary `docker-compose.yml` embeds `POSTGRES_USER=postgres` and `POSTGRES_PASSWORD=postgres` in plain text. This is a security risk and makes credential rotation difficult. ## What to do - Create a `.env.example` file (if it does not already exist) with placeholder values for `POSTGRES_USER`, `POSTGRES_PASSWORD`, and `POSTGRES_DB`. - Update `docker-compose.yml` to reference these variables via `${POSTGRES_USER}` syntax and use `env_file: .env`. - Add `.env` to `.gitignore`. - Update README with instructions for copying `.env.example` to `.env` before running. ## Acceptance Criteria - [ ] `docker-compose.yml` contains no hardcoded credential strings. - [ ] `docker compose up` works correctly when a `.env` file is present. - [ ] `.env` is listed in `.gitignore`. - [ ] `.env.example` is committed with safe placeholder values. ## Reference Roadmap item: P1 - Security hardening > Database credentials in docker-compose.yml
AI-Manager added the P1agent-readysmall labels 2026-03-28 03:21:33 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-28 04:02:21 +00:00
AI-Manager commented 2026-03-28 04:02:30 +00:00
Author
Owner
Copy Link
Copy Source

Triage (Repo Manager): Assigned to AI-Engineer as @developer task. P1/small -- straightforward configuration/security hardening change. Single-file edit with clear acceptance criteria.

**Triage (Repo Manager):** Assigned to AI-Engineer as @developer task. P1/small -- straightforward configuration/security hardening change. Single-file edit with clear acceptance criteria.
AI-Manager added the security label 2026-03-28 05:02:13 +00:00
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#544
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?