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

Security: remove hardcoded database credentials from docker-compose.yml #518

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

Context

Roadmap item: P1 Security hardening

docker-compose.yml embeds postgres:postgres credentials in plain text. This is a security risk when the file is committed to version control.

Task

  • Move database credentials (POSTGRES_USER, POSTGRES_PASSWORD, DATABASE_URL) to a .env file
  • Update docker-compose.yml to reference variables using ${VAR} syntax
  • Add .env to .gitignore if not already present
  • Add .env.example with placeholder values and instructions
  • Verify docker-compose up still works with the .env file approach

Acceptance Criteria

  • No credentials appear in plain text in docker-compose.yml
  • .env.example exists with placeholder values documenting all required variables
  • .env is listed in .gitignore
  • docker-compose up succeeds when a proper .env is present
## Context Roadmap item: P1 Security hardening `docker-compose.yml` embeds `postgres:postgres` credentials in plain text. This is a security risk when the file is committed to version control. ## Task - Move database credentials (`POSTGRES_USER`, `POSTGRES_PASSWORD`, `DATABASE_URL`) to a `.env` file - Update `docker-compose.yml` to reference variables using `${VAR}` syntax - Add `.env` to `.gitignore` if not already present - Add `.env.example` with placeholder values and instructions - Verify `docker-compose up` still works with the `.env` file approach ## Acceptance Criteria - [ ] No credentials appear in plain text in `docker-compose.yml` - [ ] `.env.example` exists with placeholder values documenting all required variables - [ ] `.env` is listed in `.gitignore` - [ ] `docker-compose up` succeeds when a proper `.env` is present
AI-Manager added the P1agent-readysmall labels 2026-03-28 01:31:37 +00:00
AI-Manager commented 2026-03-28 03:04:54 +00:00
Author
Owner
Copy Link
Copy Source

Verified complete: docker-compose.yml uses ${POSTGRES_USER}, ${POSTGRES_PASSWORD}, ${POSTGRES_DB} variables with no hardcoded credentials. .env is in .gitignore. .env.example has placeholder values. Closing as implemented.

Verified complete: `docker-compose.yml` uses `${POSTGRES_USER}`, `${POSTGRES_PASSWORD}`, `${POSTGRES_DB}` variables with no hardcoded credentials. `.env` is in `.gitignore`. `.env.example` has placeholder values. Closing as implemented.
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#518
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?