DefangLabs / DefangLabs/samples
Local dev files
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 12
- Forks
- 27
- Avg merge
- 3h 30m
- Merged PRs (30d)
- 36
Description
I propose that we stop using compose.dev.yaml and instead use compose.local.yaml as a convention for local dev. It's common enough to have a dev deployment for features that are still in development and since we're going down the path of using different compose files for different environments, it would make sense to use compose.dev.yaml for the cloud dev environment and compose.local.yaml for the local dev setup.
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
Search the repository for compose.dev.yaml and compose.local.yaml references, then inspect the compose files and any documentation or commands that use them. Done means local development consistently uses compose.local.yaml, while the dev-environment convention remains available as described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose
- Domain
- devops
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100