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

New Issue
Closed
opened 2026-03-28 15:22:00 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 15:22:00 +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 access to the repository can read them.

Work to do

  • Create a .env.example file (if not already present) with placeholder values for POSTGRES_USER, POSTGRES_PASSWORD, and POSTGRES_DB
  • Update docker-compose.yml to reference these variables using ${POSTGRES_USER} syntax
  • Ensure .env is listed in .gitignore
  • Update developer setup documentation to instruct copying .env.example to .env

Acceptance criteria

  • docker-compose.yml contains no hardcoded credentials
  • Running docker compose up with a populated .env starts Postgres successfully
  • .env is ignored by git; .env.example is tracked
  • README or CONTRIBUTING reflects the updated setup steps
## Context Roadmap item: P1 Security hardening `docker-compose.yml` embeds `postgres:postgres` credentials in plain text. Anyone with access to the repository can read them. ## Work to do - Create a `.env.example` file (if not already present) with placeholder values for `POSTGRES_USER`, `POSTGRES_PASSWORD`, and `POSTGRES_DB` - Update `docker-compose.yml` to reference these variables using `${POSTGRES_USER}` syntax - Ensure `.env` is listed in `.gitignore` - Update developer setup documentation to instruct copying `.env.example` to `.env` ## Acceptance criteria - `docker-compose.yml` contains no hardcoded credentials - Running `docker compose up` with a populated `.env` starts Postgres successfully - `.env` is ignored by git; `.env.example` is tracked - README or CONTRIBUTING reflects the updated setup steps
AI-Manager added the P1agent-readysmallsecurity labels 2026-03-28 15:22:00 +00:00
AI-Manager commented 2026-03-28 16:03:17 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already implemented. Hardcoded database credentials were removed from docker-compose.yml and replaced with environment variable references (${POSTGRES_USER}, ${POSTGRES_PASSWORD}, etc.). Added in PR #27 (feature/p1-security-hardening).

Closing as already implemented. Hardcoded database credentials were removed from docker-compose.yml and replaced with environment variable references (${POSTGRES_USER}, ${POSTGRES_PASSWORD}, etc.). Added in PR #27 (feature/p1-security-hardening).
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#685
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?