00:03
Node-RED is made by IBM Emerging Technology to automate the internet of
00:08
things that can be installed on cloud servers, raspberry PI's and most Windows,
00:12
Mac, and Linux systems. Most instances of Node-RED are insecure but the groov box
00:17
industrial IoT and operator interface appliance adds extra security through
00:21
HTTPS and authentication. The groov box also adds an extra feature that helps
00:26
you maintain and monitor Node-RED called Node-RED Admin. In this workshop
00:31
I'll show you the amazing features and added security it provides.
00:40
Now Node-RED and Node-RED Admin are already running on the groov AR1 by
00:45
default. The first thing I'm going to show you in this video is Node-RED Admin
00:50
to get to the admin landing page head on over to HTTPS colon slash slash your
00:56
groov box's hostname or IP address colon 3000. Here you'll need to login
01:02
with your groov Admin users account. Operator, Editor and Kiosk accounts are
01:07
not permitted to use Node-RED Admin.From here you can see the groov Box's uptime,
01:12
relevant status data like memory and CPU usage, version numbers, and also start and
01:18
stop Node-RED. This feature is especially useful since
01:23
you'll want to restart Node-RED after installing new node packages. Clicking
01:27
this large button here will take you straight to the Node-RED editor webpage.
01:32
Notice that when the page launches it is using HTTPS and you have to authenticate
01:37
again which is protecting your Node-RED editor.
01:44
Back to Node-RED Admin. The other features have spread across these tabs
01:49
on the left.Let's go to project management. Here you can export the
01:55
project as a file in JavaScript object notation or JSON format as well as
02:00
upload an entire project which will override the current project.
02:03
Below that is credentials which holds an encrypted string containing the
02:07
sensitive node information like usernames and passwords that are not
02:11
included when you export and import flows normally through the clipboard. You
02:15
can either download or override these files or view them using these buttons.
02:18
Here's what an encrypted credentials file may look like and here's what my
02:23
flows look like through a web browser JSON plugin. If you want to start fresh
02:27
you can download and backup your flows and credentials files and delete the
02:31
entire project from here to get an empty instance of Node-RED.
02:34
But, you'll still be able to fully restore your lost project using these
02:37
upload options. The certificates page is used to supply node read with SSL
02:43
certificates to use over HTTPS. For more information on this check out the groov
02:48
Box's user guide on Opto22.com. If you're not using HTTPS don't worry about
02:54
this section. Finally there's the Diagnostics page which is where you can
02:58
view a live console.log from Node-RED which is very useful for debugging and
03:03
understanding what is going on behind the scenes. You can also set debug nodes
03:06
to output messages to this stream as well as use the debug tab of the output
03:10
pane in Node-RED. The console log goes a lot further back, shows extra messages
03:15
like when an email node checks an inbox. This feed can be downloaded to file
03:19
using this button here or viewed as a static page. So there you have it
03:24
the Node-RED Admin page on the groov box is a very powerful and easy way to
03:28
manage your Node-RED instance on this hardened appliance. Thank you for
03:32
watching.