Blazor webapp #96
Open
Blazor webapp #96
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
…ation and authorization
…vault code display
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.
This adds a Blazor WASM app which offers the same functionality as the current Angular WebApp in this repo.
The goal was to make this a PWA app, which I managed to do, however, PWA's are only supported from trusted HTTPS servers, and as the API this app needs to call is on a private network, it's not possible to obtain a commonly trusted certificate for the API. If the app runs on HTTPS the browser also refuses to make any calls to non-HTTPS services, effectively breaking the functionality of the app.
So no HTTPS == no PWA
Nevertheless I put quite some effort into this to give the app a nice UI, and added a connection check so you can't press the door button if the API isn't reachable etc...