Updating Wizarr Subdomain Config #784
Open
Conversation
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
Adding specific auth exemption location blocks as expected based on https://docs.wizarr.dev/using-wizarr/single-sign-on-sso
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.
Adding specific auth exemption location blocks as expected based on Wizarr Docs.
Description
Updating the Wizarr Subdomain configuration to include specific location blocks for the join, j, static, setup, wizard, image-proxy, and cinema-posters api paths required for use.
Benefits of this PR and context
Wizarr is a popular application used to streamline inviting users to personal media servers. This PR updates the default sample to match the instructions as provided by the official documentation.
How Has This Been Tested?
This set of changes have been tested on my personal devices. I can confirm nginx is able to start and the service functions as expected. There are no build or lint tests associated with this project.
Source / References
Official Docs