#NODE RED CONTRIB IMAGE TOOLS INSTALL#

Now Xvfb can be enabled and starting by issuing the following commands: User and Group should be set to the same user and group that node-red runs under. In order to do that, create a file at /etc/systemd/system/rvice with the following contents:ĭescription=X Virtual Frame Buffer ServiceĮxecStart=/usr/bin/Xvfb :0 -screen 0 1024x768x24 -ac +extension GLX +render -noreset Xvfb should have been installed along with the previous command such that it is only necessary to create a way to start the graphics manager in the background. Since the purpose of this project is to run in headless mode with just node-red as the main interface, a virtual graphics manager Xvfb will be used to start a virtual X session in the background and run the various browsers automatically that will be used by Selenium and the node-red-contrib-selenium-webdrive package. By consequence, Selenium requires that a graphics manager is available and running, such as Xorg. Selenium is a browser automation package that uses real browsers and performs actions such as clicking on HTML elements, executing JavaScript, finding elements, etc.

#NODE RED CONTRIB IMAGE TOOLS INSTALL#

Node-red-contrib-selenium-webdriver requires a bunch of packages that must be installed to work, namely the following command would have to be executed on a Debian system:Īpt-get install -y xvfb x11-xkb-utils xfonts-100dpi xfonts-75dpi xfonts-scalable xfonts-cyrillic x11-apps clang libdbus- 1-dev libgtk2.0-dev libnotify-dev libgnome-keyring-dev libgconf2-dev libasound2-dev libcap-dev libcups2-dev libxtst-dev libxss1 libnss3-dev gcc-multilib g++-multilib default-jre-headless Npm -g install node-red-contrib-selenium-webdriver node-red-contrib-amazon-echo The next step is to install the rest of the required modules: The systemd service can then be enabled and started by issuing the commands: # Note RHEL/Fedora uses 'root', Debian/Ubuntu uses 'nogroup' Then create a file at /etc/systemd/system/rvice that will be responsible for automatically starting node-red on boot with the following contents: One solution to this problem is to create a virtual machine and dedicate it to node-red to ensure that there are no interferences with Apache or other services that may be listening on the local network.Īnd create a user and group pair, say, named node-red to run node-red under.

When Alexa scans the network, it will only discover node-red-contrib-amazon-echo when it is listening on port 80. One drawback is that it is imperative that TCP port 80 is available to be used. The node-red-contrib-amazon-echo module runs locally and does not use an Alexa app hosted with Amazon.

Node red contrib image tools