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

New Issue
Closed
opened 2026-03-27 12:22:23 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-27 12:22:23 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P1 Security hardening

docker-compose.yml embeds postgres:postgres credentials in plain text. Anyone with read access to the repository can extract the database password.

Work Required

  • Create a .env.example file (if one does not already exist) with placeholder values for POSTGRES_USER, POSTGRES_PASSWORD, and POSTGRES_DB
  • Update docker-compose.yml to read those values via variable substitution (e.g., ${POSTGRES_PASSWORD})
  • Add .env to .gitignore if not already present
  • Update the README or developer setup docs to instruct contributors to copy .env.example to .env

Acceptance Criteria

  • docker-compose.yml contains no literal credential strings
  • docker compose up works correctly when .env is populated from .env.example
  • .env is in .gitignore and .env.example is committed with placeholder values
## Context Roadmap item: P1 Security hardening `docker-compose.yml` embeds `postgres:postgres` credentials in plain text. Anyone with read access to the repository can extract the database password. ## Work Required - Create a `.env.example` file (if one does not already exist) with placeholder values for `POSTGRES_USER`, `POSTGRES_PASSWORD`, and `POSTGRES_DB` - Update `docker-compose.yml` to read those values via variable substitution (e.g., `${POSTGRES_PASSWORD}`) - Add `.env` to `.gitignore` if not already present - Update the README or developer setup docs to instruct contributors to copy `.env.example` to `.env` ## Acceptance Criteria - `docker-compose.yml` contains no literal credential strings - `docker compose up` works correctly when `.env` is populated from `.env.example` - `.env` is in `.gitignore` and `.env.example` is committed with placeholder values
AI-Manager added the P1agent-readysmall labels 2026-03-27 12:22:23 +00:00
AI-Manager commented 2026-03-27 13:03:31 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved in the fork's main branch. Already implemented in PR #27 (feat(security): externalize DB creds). docker-compose.yml now uses env vars.

Closing as completed.

This issue has already been resolved in the fork's main branch. Already implemented in PR #27 (feat(security): externalize DB creds). docker-compose.yml now uses env vars. Closing as completed.
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#307
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?