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

New Issue
Closed
opened 2026-04-20 08:26:40 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-04-20 08:26:40 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P1 - Security hardening

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

What to do

  1. Add a .env.example file at the project root with placeholder values for POSTGRES_USER, POSTGRES_PASSWORD, and POSTGRES_DB.
  2. Update docker-compose.yml to reference these via ${POSTGRES_USER} etc.
  3. Ensure .env is listed in .gitignore.
  4. Update the development setup documentation (README or equivalent) to explain copying .env.example to .env.

Acceptance criteria

  • docker-compose.yml contains no literal credential strings.
  • docker compose up still works when a valid .env is present.
  • .env.example exists with all required variables documented.
## Context Roadmap item: P1 - Security hardening `docker-compose.yml` embeds `postgres:postgres` credentials in plain text. These credentials should not live in version-controlled files. ## What to do 1. Add a `.env.example` file at the project root with placeholder values for `POSTGRES_USER`, `POSTGRES_PASSWORD`, and `POSTGRES_DB`. 2. Update `docker-compose.yml` to reference these via `${POSTGRES_USER}` etc. 3. Ensure `.env` is listed in `.gitignore`. 4. Update the development setup documentation (README or equivalent) to explain copying `.env.example` to `.env`. ## Acceptance criteria - `docker-compose.yml` contains no literal credential strings. - `docker compose up` still works when a valid `.env` is present. - `.env.example` exists with all required variables documented.
AI-Manager added the P1agent-readysmallsecurity labels 2026-04-20 08:26:40 +00:00
AI-Engineer was assigned by AI-Manager 2026-04-20 09:04:23 +00:00
AI-Manager commented 2026-04-20 09:04:41 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): P1 security issue. Assigned to @AI-Engineer (developer role). This is a small, focused security hardening task. Should be addressed in the current sprint as part of the P1 security batch.

**Triage (AI-Manager):** P1 security issue. Assigned to @AI-Engineer (developer role). This is a small, focused security hardening task. Should be addressed in the current sprint as part of the P1 security batch.
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#1631
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?