flask demo: don't provide a meaningless default server #163
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.
Instead, ask the user to provide the test server. Which is annoying, but...
The flask demo needs an OAuth-capable server, and we are currently using a no-auth server, so the user just sees a message "nothing to demo here".
This is because:
All of the public test servers I know about require you to email someone to set up a user. So it's not obvious what a good replacement would be.
Honestly, we should probably just add a new default demo that supports no-auth servers and still shows something interesting.
But for now, this gets the flask demo to a more honest place and asks the user to provide their own server. 🤷
Fixes #162
Fixes #86