Deploying RedBot

🏴‍☠️ Under construction…

Environment variables

Variable	Default	Description
NODE_RED_ENABLE_SAFE_MODE	false	Execute Node-RED in safe mode: the flow is stopped. Useful in case the flow start looping or crashes at startup.
NODE_RED_ENABLE_PROJECTS	false	Enable projects in Node-RED
NODE_RED_NON_HEADLESS
NODE_RED_FUNCTION_TIME
NODE_RED_HOME
NODE_RED_ENABLE_TOURS	true	Enable or disable on-boarding tour at startup
PORT	1880	Node-RED port
REDBOT_ENABLE_MISSION_CONTROL	false	Enable Mission Control (true or false, default is false)
REDBOT_DB_PATH	`<userdir>`
REDBOT_ENVIRONMENT	development	Define the environment for the chatbot. In production RedBot will only use “production” configurations. See
REDBOT_DEVELOPMENT_MODE	production	Tells where to take the front-end assets (only for plugin developers)
In production uses bundled and compiled assets.
In plugin uses development assets except plugins.
In development both core and plugin codes are served by the local dev server.

NodeRED settings file

tbc

environment	development
dbPath
enableMissionControl

Docker

tbd

docker run -it -p 1880:1880 -v /Users/guido/web/docker-redbot:/data --name myredbot guidone/redbot

RedBot environment

All sender/receiver nodes have a double bot configuration for development and production. By default is used the development configuration. To use production configuration, edit Node-RED settings file (settings.js) and set the environment global variable to "production".

{
  // ...
  functionGlobalContext: {
    environment: 'development',
    // ...
  }
}

In this way the same Node-RED project (the same git repository) will work in two different environments without changes. Deploying the chatbot to production will require just a couple of clicks:

After all changes to the local chatbot are complete, go to the History > Local Changes panel of Node-RED and the commit all changes