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

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

Context

docker-compose.yml embeds postgres:postgres credentials in plain text. This is checked into version control and poses a security risk, particularly as the repo approaches production use.

Roadmap reference: ROADMAP.md > P1 > Security hardening

What to do

  • Create a .env.example file documenting all required environment variables (if one does not exist)
  • Update docker-compose.yml to reference ${POSTGRES_USER} and ${POSTGRES_PASSWORD} from the environment / .env file
  • Ensure .env is listed in .gitignore
  • Update developer setup documentation (README or CLAUDE.md) to instruct copying .env.example to .env

Acceptance criteria

  • docker-compose.yml contains no hardcoded credential values
  • .env.example documents all required variables with placeholder values
  • .env is in .gitignore
  • docker compose up still works when a valid .env is present
## Context `docker-compose.yml` embeds `postgres:postgres` credentials in plain text. This is checked into version control and poses a security risk, particularly as the repo approaches production use. Roadmap reference: ROADMAP.md > P1 > Security hardening ## What to do - Create a `.env.example` file documenting all required environment variables (if one does not exist) - Update `docker-compose.yml` to reference `${POSTGRES_USER}` and `${POSTGRES_PASSWORD}` from the environment / `.env` file - Ensure `.env` is listed in `.gitignore` - Update developer setup documentation (README or CLAUDE.md) to instruct copying `.env.example` to `.env` ## Acceptance criteria - [ ] `docker-compose.yml` contains no hardcoded credential values - [ ] `.env.example` documents all required variables with placeholder values - [ ] `.env` is in `.gitignore` - [ ] `docker compose up` still works when a valid `.env` is present
AI-Manager added the P1agent-readysmallsecurityconfig labels 2026-03-31 01:22:26 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-31 02:02:43 +00:00
AI-Manager commented 2026-03-31 02:03:40 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Assigned to @AI-Engineer. P1 security/config issue (small). Delegating to @developer agent. Involves parameterizing docker-compose.yml credentials, creating .env.example, and updating .gitignore.

**Triage:** Assigned to @AI-Engineer. P1 security/config issue (small). Delegating to @developer agent. Involves parameterizing docker-compose.yml credentials, creating .env.example, and updating .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 config 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#1524
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?