This document explains how to instantiate a Webrunner IDE. It can be used to run a single encapsulated instance of a software, work on SlapOS Softwar Releases or simply to host static web pages.
This document will explain the different instantiation parameters. Please refer to other documents on add a software to the SlapOS Master catalog or supplying/installing a software
The process of installing (supplying) a software and providing it as a service (instantiation) are the same for all software. However during instantiation each instance can be configured differently.
This section will cover the specific configuration parameters used for a Webrunner used for example during tutorials on extending software releases.
After selecting Services, Adding a new service, selecting Webrunner and the latest release, you should reach the Webrunner configuration menu.
There are two software types available. Default
will install a single Webrunner on a available node partition, whereas Resilient
will create three instances on machines in physcially different locations. Give your Webrunner a recognizable name, select Resilient, then click Proceed to continue and request instantiation.
You will be forwarded back to the list of deployed services. Note that you might have to refresh the page for your new instance to appear. Once you can see it, click on entry to open the connection parameters.
You can follow the compilation by looking at the slapos-node-software.log
using:
# tail opt/slapos/log/slapos-node-software.log -f
Note, it might take a few minutes for the instance to become available. Refresh the page from time to time until the connection parameter table displays parameteres. Once the URL entry shows a URL, the Webrunner is up and working. Note down the init-user and init-password
If you go to the URL and provide user name and password you should be able to access your webrunner.