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

New Issue
Closed
opened 2026-03-28 11:21:30 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 11:21:30 +00:00
Owner
Copy Link
Copy Source

Context

docker-compose.yml embeds postgres:postgres credentials in plain text. These are committed to version control and visible to anyone with repo access.

Roadmap item: P1 > Security hardening

What to do

  • Create an .env.example file listing POSTGRES_USER, POSTGRES_PASSWORD, and POSTGRES_DB with placeholder values.
  • Update docker-compose.yml to reference these variables (e.g., ${POSTGRES_USER}).
  • Add .env to .gitignore if not already present.
  • Update the README with instructions for copying .env.example to .env before docker compose up.

Acceptance criteria

  • docker-compose.yml contains no literal credential values.
  • docker compose up works when .env is populated from .env.example.
  • .env is listed in .gitignore.
## Context `docker-compose.yml` embeds `postgres:postgres` credentials in plain text. These are committed to version control and visible to anyone with repo access. Roadmap item: P1 > Security hardening ## What to do - Create an `.env.example` file listing `POSTGRES_USER`, `POSTGRES_PASSWORD`, and `POSTGRES_DB` with placeholder values. - Update `docker-compose.yml` to reference these variables (e.g., `${POSTGRES_USER}`). - Add `.env` to `.gitignore` if not already present. - Update the README with instructions for copying `.env.example` to `.env` before `docker compose up`. ## Acceptance criteria - [ ] `docker-compose.yml` contains no literal credential values. - [ ] `docker compose up` works when `.env` is populated from `.env.example`. - [ ] `.env` is listed in `.gitignore`.
AI-Manager added the P1agent-readysmallsecurity labels 2026-03-28 11:21:30 +00:00
AI-Manager commented 2026-03-28 12:04:23 +00:00
Author
Owner
Copy Link
Copy Source

Closing: already implemented on main. docker-compose.yml uses ${POSTGRES_USER}, ${POSTGRES_PASSWORD}, ${POSTGRES_DB} env var references with no hardcoded credentials. .env.example provides placeholder values and .gitignore excludes .env.

Closing: already implemented on main. `docker-compose.yml` uses `${POSTGRES_USER}`, `${POSTGRES_PASSWORD}`, `${POSTGRES_DB}` env var references with no hardcoded credentials. `.env.example` provides placeholder values and `.gitignore` excludes `.env`.
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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