support for modification to global config via user supplied sed script
Nobody has claimed this yet.
- #32 by @kosciCZ — closed without merging
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- nginx, shell
- Domain
- devops, infrastructure
Research direction
Use the referenced httpd image's s2i/bin/assemble file as the model, then locate the nginx image's assembly and global-configuration entry points. Determine how a user-supplied sed script should be accepted and applied, and verify that it can create a server block such as /nginx_status.
Written by the indexing model from the issue text.
Description
The httpd image has support for developer provided sed input that can override the global config.
Can the nginx image be altered so a similar mechanism can be used to do things like enable /nginx_status with the server { } block?
- Dominant language
- Shell
- Stars
- 102
- Forks
- 194
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from sclorg/nginx-container
-
Cleanup /tmp/srcOpen
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
sclorg/nginx-container#329 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
sclorg/nginx-container#254 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
sclorg/nginx-container#240 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
sclorg/nginx-container#151 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
sclorg/nginx-container#105 · 1 reaction ·
All issues in sclorg/nginx-container
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
area:docs phase:release priority:p0 type:test
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
premises-missing
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
WingedGuardian/GENesis-AGI#3917 ·
Maintainers usually reply within 1 day
-
needs-device
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Non-root first start logs "Base venv updated (stamp mismatch)" instead of the first-run messageOpenarea: infrastructure bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
snapotter-hq/SnapOtter#4573 ·
Maintainers usually reply within 1 day