WSU-Software-Development-Club / WSU-Software-Development-Club/self-hosting
Move compose credentials and ports into a .env file
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Why
Postgres credentials and ports are hardcoded in docker-compose.yml. A .env file lets everyone configure their local setup without editing tracked files, and mirrors how real deployments handle config.
Files to touch
docker-compose.yml.env.example(new).gitignore
Definition of done
- Compose reads
POSTGRES_USER,POSTGRES_PASSWORD,POSTGRES_DB, and any exposed ports from.env -
.env.exampleis committed with a comment explaining every variable -
.envis gitignored -
cp .env.example .env && docker compose upworks on a fresh clone
Hints
Compose automatically loads a .env file from the project root. Use ${VAR} syntax in the YAML. Docs: https://docs.docker.com/compose/environment-variables/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docker-compose.yml and inspect the existing hardcoded Postgres credentials and exposed ports. Read Docker's Compose environment-variable documentation, then update docker-compose.yml, add the documented variables to .env.example, and check .gitignore. Verify the definition of done with cp .env.example .env && docker compose up from a fresh-clone setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 88/100