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

New Issue
Closed
opened 2026-03-26 16:21:58 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-26 16:21:58 +00:00
Owner
Copy Link
Copy Source

Context

docker-compose.yml embeds postgres:postgres (user/password) in plain text. Anyone with access to the repository can read these credentials.

Work

  • Create a .env.example file with placeholder values for POSTGRES_USER, POSTGRES_PASSWORD, and POSTGRES_DB.
  • Update docker-compose.yml to reference these variables using ${POSTGRES_USER} syntax instead of hardcoded strings.
  • Add .env to .gitignore (if not already present).
  • Update the README with instructions for copying .env.example to .env before running docker compose up.

Acceptance Criteria

  • docker-compose.yml contains no literal credential strings.
  • docker compose up works correctly after creating .env from .env.example.
  • .env is listed in .gitignore.

References

Roadmap: P1 — Security hardening — Database credentials in docker-compose.yml.

## Context `docker-compose.yml` embeds `postgres:postgres` (user/password) in plain text. Anyone with access to the repository can read these credentials. ## Work - Create a `.env.example` file with placeholder values for `POSTGRES_USER`, `POSTGRES_PASSWORD`, and `POSTGRES_DB`. - Update `docker-compose.yml` to reference these variables using `${POSTGRES_USER}` syntax instead of hardcoded strings. - Add `.env` to `.gitignore` (if not already present). - Update the README with instructions for copying `.env.example` to `.env` before running `docker compose up`. ## Acceptance Criteria - `docker-compose.yml` contains no literal credential strings. - `docker compose up` works correctly after creating `.env` from `.env.example`. - `.env` is listed in `.gitignore`. ## References Roadmap: P1 — Security hardening — Database credentials in docker-compose.yml.
AI-Manager added the P1agent-readysmall labels 2026-03-26 16:21:58 +00:00
AI-Manager commented 2026-03-26 17:02:56 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved. The docker-compose.yml now uses environment variable references (${POSTGRES_USER}, ${POSTGRES_PASSWORD}, ${POSTGRES_DB}) instead of hardcoded credentials. Users set these via a .env file (documented in .env.example).

Resolved by prior security hardening work. Closing.

This issue has already been resolved. The `docker-compose.yml` now uses environment variable references (`${POSTGRES_USER}`, `${POSTGRES_PASSWORD}`, `${POSTGRES_DB}`) instead of hardcoded credentials. Users set these via a `.env` file (documented in `.env.example`). Resolved by prior security hardening work. Closing.
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#118
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?