nginx-proxy / nginx-proxy/docker-gen
Allow docker-gen to be used as a library
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4.6k
- Forks
- 609
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 4
Description
As discussed briefly at https://github.com/jwilder/docker-gen/pull/130 and https://github.com/jwilder/nginx-proxy/pull/254, it could be beneficial to restructure docker-gen to be usable both as a standalone binary and as an embedded library.
I'm opening this issue as a place to discuss the details of such a change.
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 by reviewing the issue discussion and the linked docker-gen pull request #130 and nginx-proxy pull request #254. The payload names no files, tests, or entry points, so first identify how the standalone binary is structured and what an embedded-library interface would need. Done means an agreed design and a restructuring that supports both use cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100