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

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

Context

Roadmap item: P1 Security Hardening

docker-compose.yml embeds postgres:postgres in plain text. Credentials should not live in version-controlled compose files.

What to do

  • Remove the hardcoded POSTGRES_USER, POSTGRES_PASSWORD, and related values from docker-compose.yml
  • Reference a .env file instead using the env_file directive or Docker Compose variable interpolation (${POSTGRES_PASSWORD})
  • Create a .env.example file (if it does not already exist) with placeholder values and documentation
  • Ensure .env is listed in .gitignore

Acceptance criteria

  • docker-compose.yml contains no hardcoded database credentials
  • docker-compose up works correctly when .env is populated from .env.example
  • .env is ignored by git
  • .env.example documents all required variables
## Context Roadmap item: P1 Security Hardening `docker-compose.yml` embeds `postgres:postgres` in plain text. Credentials should not live in version-controlled compose files. ## What to do - Remove the hardcoded `POSTGRES_USER`, `POSTGRES_PASSWORD`, and related values from `docker-compose.yml` - Reference a `.env` file instead using the `env_file` directive or Docker Compose variable interpolation (`${POSTGRES_PASSWORD}`) - Create a `.env.example` file (if it does not already exist) with placeholder values and documentation - Ensure `.env` is listed in `.gitignore` ## Acceptance criteria - `docker-compose.yml` contains no hardcoded database credentials - `docker-compose up` works correctly when `.env` is populated from `.env.example` - `.env` is ignored by git - `.env.example` documents all required variables
AI-Manager added the P1agent-readysmallsecurity labels 2026-03-28 12:21:49 +00:00
AI-Manager commented 2026-03-28 13:03:13 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already resolved. docker-compose.yml uses ${POSTGRES_PASSWORD}, ${POSTGRES_USER}, and ${POSTGRES_DB} environment variable references -- no hardcoded credentials. Users set values via .env file per the documented workflow.

Closing as already resolved. `docker-compose.yml` uses `${POSTGRES_PASSWORD}`, `${POSTGRES_USER}`, and `${POSTGRES_DB}` environment variable references -- no hardcoded credentials. Users set values via `.env` file per the documented workflow.
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#639
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?