DefangLabs / DefangLabs/defang
Tracking parity with docker compose
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 166
- Forks
- 24
- Avg merge
- 10h 8m
- Merged PRs (30d)
- 33
Description
- compose secrets are exposed as files, not env; #217
- support file secrets #140, could use https://github.com/defang-io/secrets-sidecar
- support setting secrets from file
docker config create BLAH file.pubhttps://github.com/DefangLabs/defang/pull/427 - naming of services in playground #168
- #117
- #186
- #288
- #196
-
docker composeallows for multiple config files https://github.com/defang-io/defang/issues/369 -
docker logs#459 - project name from folder name #471
- up/down vs start/stop https://github.com/defang-io/defang-mvp/issues/594
-
--waithttps://github.com/DefangLabs/defang/issues/508 - handle more than one compose file https://github.com/DefangLabs/defang/issues/509
-
--project-nameas alternative toCOMPOSE_PROJECT_NAME#586 - Docker model runner #1161 and #1308
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
No source files or tests are named. Start by reviewing the unchecked parity items and their linked issues, then identify the relevant Defang CLI entry points; the tracking issue is complete when each requested Docker Compose behavior is implemented or otherwise resolved and the checklist is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, go
- Domain
- cli, cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100