feat: add INGRESS_TOKEN env variable to set the ingress session cookie #3892
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
3 tasks
Pull Request Test Coverage Report for Build 10872120036Details
💛 - Coveralls |
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.
SERVER_URL=https://192.168.1.x:8123/api/hassio_ingress/abcdefg INGRESS_TOKEN=123456789 npm run devI needed a way to connect my local development frontend to the remote zwave-js-ui backend. Since the HASSIO docker container doesn't expose the port to the host the easiest way around it is via Hass.io Ingress. Unfortunately that needs cookie authentication, which can be easily injected via Vite's built-in proxy. This PR adds an
INGRESS_TOKENenv variable where you can specify the token and it will take care of injecting the cookie for each API request. Use Chrome/Firefox DevTools to figure out what's the correct IngressSERVER_URLandINGRESS_TOKEN.