frodovdr/node-red
1
0
Fork 0
mirror of https://github.com/node-red/node-red.git synced 2023-10-10 13:36:53 +02:00
Code Issues Releases Wiki Activity

Updated Design: Runnable Project (markdown)

Dave Conway-Jones 2018-03-28 13:44:23 +01:00
parent 8c623005fc
commit 76677e65f4
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Design:-Runnable-Project.md

@ -20,7 +20,11 @@ We can't quite do this today. Here are the missing pieces:
3. it must be possible to provide the credentialSecret for the project without it being part of any of the version controlled files. Options for this include:
- env var - `NODE_RED_CREDENTIAL_SECRET`
- command-line flag - `--credentialSecret="..."`
4. Must handle running in a read-only environment. If the package is installed globally (in order to insert a command link into /usr/bin) then the flow file and settings.js will be in root space - which ought not to be writable by the user. Currently even starting Node-RED with -u option pointing somewhere protected will fail. Options include - just handling the error. On error marking the settings.readOnly as true thus stopping the library failing. Setting disableEditor to true also.
4. Must handle running in a read-only environment. If the package is installed globally (in order to insert a command link into /usr/bin) then the flow file and settings.js will be in root space - which ought not to be writable by the user. Currently even starting Node-RED with -u option pointing somewhere protected will fail. Options include
- just handling the error.
- on detecting this condition, marking the settings.readOnly as true thus stopping the library failing.
- setting disableEditor to `true` also.
The package would provide an npm start script that runs node-red with the appropriate command-line args.
It could also provide a `bin` section that could allow starting via command line if installed globally.