nginx-proxy / nginx-proxy/nginx-proxy
Nginx configuration by environment variables
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19.9k
- Forks
- 3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 1
Description
Currently if we want to add or override some config files we need to build our own image (usually Dockerfile with 2 lines).
How about to add possibility to insert configuration by env variables?
Example docker-compose.yml:
environment:
CONFIG_GLOBAL: "client_max_body_size 50M;"
CONFIG_WWW_EXAMPLE_COM: "client_body_buffer_size 10m;"
CONFIG_GLOBAL_LOCATION: "client_max_body_size 50M;"
CONFIG_WWW_EXAMPLE_COM_LOCATION: |
client_body_buffer_size 10m;
client_max_body_size 50M;
This variables will be printed in the right place by template.
Is PR welcome?
This feature will probably decrease need for adding other single-use-case features.
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 the example docker-compose.yml and the Nginx template mentioned in the issue. Trace how environment variables are currently passed into template generation, then define how CONFIG_GLOBAL, CONFIG_WWW_EXAMPLE_COM, and their LOCATION variants should be inserted; done means those values appear in the appropriate generated configuration locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, nginx
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100