Open
Conversation
gsanchietti
force-pushed
the
separate_nginx
branch
from
61aa5d1 to
6f33ec5
Compare
Let's stick to upstream nginx to be sure to gather latest security patches.
gsanchietti
force-pushed
the
separate_nginx
branch
from
6f33ec5 to
2b990c2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Let's stick to upstream nginx to be sure to gather latest security patches from OpenWrt.
Please note that nginx on OpenWrt platform often lags behind official releases.
After some tests, I've found that the new
ns-reverse-proxyis enabled on boot on new installations and after an image upgrade.If we want to update existing machines using packages, we must add ns-reverse-proxy as a dependency of an existing package (eg. ns-plug or ns-api). Merge only when ready to be released
Fix #1506