let uiHost be set by security question in admin init. Beef up language around security question. #32
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.
(force to 127.0.0.1 if no admin password)
Proposed changes
This change beefs up the language about choosing a password... ie by adding
" DO NOT select No if you will expose Node-RED to the internet - or you will be hacked!"
If the user then still selects no it then changes the uiHost setting to be 127.0.0.1 so that only the local browser can connect and edit by default.
This only happens when you run node-red admin init - so won't affect existing users.
In parallel - The Pi install script will change to always run admin init if there is no settings file (IE a clean install) - so it should now be almost mandatory for new (Pi/debian/ubuntu) users to set an admin password...
Checklist
grunt
to verify the unit tests pass