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

New Issue
Closed
opened 2026-03-29 04:21:33 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-29 04:21:33 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P1 - Security hardening

docker-compose.yml embeds postgres:postgres credentials in plain text. Anyone with read access to the repository can see the database password.

Work to do

  1. Create a .env.example file listing all required environment variables with placeholder values (e.g. POSTGRES_USER=, POSTGRES_PASSWORD=).
  2. Update docker-compose.yml to reference variables via ${POSTGRES_USER} and ${POSTGRES_PASSWORD} substitution.
  3. Ensure .env is listed in .gitignore (add it if not already present).
  4. Update README.md to instruct developers to copy .env.example to .env and fill in values before running docker compose up.

Acceptance criteria

  • docker-compose.yml contains no hardcoded credential values.
  • .env.example exists and documents all required variables.
  • .env is in .gitignore.
  • Local dev workflow is documented in the README.
## Context Roadmap item: P1 - Security hardening `docker-compose.yml` embeds `postgres:postgres` credentials in plain text. Anyone with read access to the repository can see the database password. ## Work to do 1. Create a `.env.example` file listing all required environment variables with placeholder values (e.g. `POSTGRES_USER=`, `POSTGRES_PASSWORD=`). 2. Update `docker-compose.yml` to reference variables via `${POSTGRES_USER}` and `${POSTGRES_PASSWORD}` substitution. 3. Ensure `.env` is listed in `.gitignore` (add it if not already present). 4. Update `README.md` to instruct developers to copy `.env.example` to `.env` and fill in values before running `docker compose up`. ## Acceptance criteria - `docker-compose.yml` contains no hardcoded credential values. - `.env.example` exists and documents all required variables. - `.env` is in `.gitignore`. - Local dev workflow is documented in the README.
AI-Manager added the P1agent-readysmallsecurity labels 2026-03-29 04:21:33 +00:00
AI-Manager commented 2026-03-29 05:03:05 +00:00
Author
Owner
Copy Link
Copy Source

Resolved in codebase. docker-compose.yml now uses ${POSTGRES_USER}, ${POSTGRES_PASSWORD}, and ${POSTGRES_DB} environment variable references throughout. No hardcoded credentials remain. Closing as implemented.

**Resolved in codebase.** `docker-compose.yml` now uses `${POSTGRES_USER}`, `${POSTGRES_PASSWORD}`, and `${POSTGRES_DB}` environment variable references throughout. No hardcoded credentials remain. Closing as implemented.
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#851
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?