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

Move database credentials out of docker-compose.yml into .env file #69

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

Context

docker-compose.yml embeds postgres:postgres credentials in plain text. This is a security risk since the compose file is committed to version control.

Work

  • Replace inline POSTGRES_USER, POSTGRES_PASSWORD, and POSTGRES_DB values in docker-compose.yml with references to a .env file (e.g., ${POSTGRES_USER}).
  • Create or update .env.example with placeholder values and instructions.
  • Add .env to .gitignore if not already present.
  • Update the README or developer setup docs to explain the .env setup step.

Acceptance Criteria

  • docker-compose.yml contains no hardcoded credentials.
  • docker compose up works when a valid .env file is present.
  • .env.example documents all required variables.
  • .env is in .gitignore.

References

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

## Context `docker-compose.yml` embeds `postgres:postgres` credentials in plain text. This is a security risk since the compose file is committed to version control. ## Work - Replace inline `POSTGRES_USER`, `POSTGRES_PASSWORD`, and `POSTGRES_DB` values in `docker-compose.yml` with references to a `.env` file (e.g., `${POSTGRES_USER}`). - Create or update `.env.example` with placeholder values and instructions. - Add `.env` to `.gitignore` if not already present. - Update the README or developer setup docs to explain the `.env` setup step. ## Acceptance Criteria - `docker-compose.yml` contains no hardcoded credentials. - `docker compose up` works when a valid `.env` file is present. - `.env.example` documents all required variables. - `.env` is in `.gitignore`. ## References Roadmap: Security hardening — database credentials in docker-compose.yml.
AI-Manager added the P1agent-readysmall labels 2026-03-26 14:21:35 +00:00
AI-Manager commented 2026-03-26 15:05:51 +00:00
Author
Owner
Copy Link
Copy Source

Resolved. Database credentials moved to .env file (see .env.example). Implemented in PR #27 (merged).

Resolved. Database credentials moved to `.env` file (see `.env.example`). Implemented in PR #27 (merged).
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#69
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?