Added option in scripts/serve.js. Updated INSTALL.MD documentation #367
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.
What is this change?
Adding a option through an environment variable (NODE_PROXY_SECURE) to set "secure: false" in the proxy config in the serve.js file. If the environment variable is not set it will default to "secure: true"
Why is this change necessary?
Current config requires a CA signed SSL certificate even in a development environment.
Have you reviewed and updated the documentation for this change? Is new documentation required?
Yes, I have updated the INSTALL.MD file.
How did you verify this change?
Deployed open source sensu web with my changes in my testing enviroment. The 500 error I was seeing no longer appeared after the change and I was allowed to connect to the sensu-backend service.
Related Issue
#362