Adding env variables for parametrized Gradio login #125
Conversation
This file contains 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
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.
For tests of WAN from multiple locations, the Gradio UI is currently open on the Internet. So, it has to be minimally protected with at least 1 same userid / password for all testers.
So, this PR activates the simple Gradio authentication when 2 ENV vars are present: WAN_USER & WAN PWD. The UI remains open as today when those vars are not present. Those env vars can be set externally at container start in docker run command when Wan is containerized,
See https://www.gradio.app/guides/sharing-your-app#authentication for details
See commit diff for the corresponding code.
I'll be happy to add same code to other Gradio demo scripts when you accept this PR.
Best,
Didier