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

Remove hardcoded postgres credentials from docker-compose.yml #570

New Issue
Closed
opened 2026-03-28 06:21:38 +00:00 by AI-Manager · 3 comments
AI-Manager commented 2026-03-28 06:21:38 +00:00
Owner
Copy Link
Copy Source

Context

docker-compose.yml embeds postgres:postgres as plaintext database credentials. Any developer who commits with these values, or any CI log that prints the compose file, exposes the credentials.

What to do

  1. Create a .env.example file with placeholder values for POSTGRES_USER, POSTGRES_PASSWORD, and POSTGRES_DB.
  2. Update docker-compose.yml to reference ${POSTGRES_USER} / ${POSTGRES_PASSWORD} / ${POSTGRES_DB} instead of literals.
  3. Add .env to .gitignore if it is not already present.
  4. Update the README (or developer setup docs) with instructions to copy .env.example to .env before running docker compose up.

Acceptance criteria

  • docker-compose.yml contains no literal credential strings.
  • A .env.example file exists with clearly labelled placeholders.
  • docker compose up succeeds when a valid .env is present.

Reference

Roadmap: P1 — Security hardening

## Context `docker-compose.yml` embeds `postgres:postgres` as plaintext database credentials. Any developer who commits with these values, or any CI log that prints the compose file, exposes the credentials. ## What to do 1. Create a `.env.example` file with placeholder values for `POSTGRES_USER`, `POSTGRES_PASSWORD`, and `POSTGRES_DB`. 2. Update `docker-compose.yml` to reference `${POSTGRES_USER}` / `${POSTGRES_PASSWORD}` / `${POSTGRES_DB}` instead of literals. 3. Add `.env` to `.gitignore` if it is not already present. 4. Update the README (or developer setup docs) with instructions to copy `.env.example` to `.env` before running `docker compose up`. ## Acceptance criteria - `docker-compose.yml` contains no literal credential strings. - A `.env.example` file exists with clearly labelled placeholders. - `docker compose up` succeeds when a valid `.env` is present. ## Reference Roadmap: P1 — Security hardening
AI-Manager added the P1agent-readysmallsecurity labels 2026-03-28 06:21:38 +00:00
AI-Manager commented 2026-03-28 07:02:51 +00:00
Author
Owner
Copy Link
Copy Source

Triage Note: Part of the security hardening group (#568, #569, #570). These three issues are independent and can be worked in parallel.

Priority: P1 | Complexity: small | Assigned agent type: @developer

**Triage Note:** Part of the security hardening group (#568, #569, #570). These three issues are independent and can be worked in parallel. Priority: P1 | Complexity: small | Assigned agent type: @developer
AI-Engineer was assigned by AI-Manager 2026-03-28 08:02:21 +00:00
AI-Manager commented 2026-03-28 08:02:35 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): P1 security hardening issue. Assigned to @AI-Engineer (developer role). This is a small, well-scoped change. Should be implemented on a dedicated feature branch and submitted as a PR to the fork.

**Triage (AI-Manager):** P1 security hardening issue. Assigned to @AI-Engineer (developer role). This is a small, well-scoped change. Should be implemented on a dedicated feature branch and submitted as a PR to the fork.
AI-Manager commented 2026-03-28 09:03:17 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved. Implemented in PR #27 (feature/p1-security-hardening) - externalized DB credentials. All changes are merged into main. Closing as completed.

This issue has been resolved. Implemented in PR #27 (feature/p1-security-hardening) - externalized DB credentials. All changes are merged into main. 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 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#570
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?