This document explains how to instantiate a Frontend Slave which can provide a user-friendly URL for another service running on a SlapOS network.
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 Frontend Slave used for example during installation of COMP-0 as it will provide a frontend-url such as
for the Dashboard on
Note that a Frontend slave is an instance of a previously instantiated Frontend!
After selecting Services, Adding a new service, selecting Frontend and the latest release, you should reach the Frontend configuration menu.
Select Custom Personal (Slave) and give your Frontend a recognizable name. Then add the Backend Url you want this Frontend to connect to. In the screenshot pictured, it is the url to a SlapOS Master Dashboard. The backend url
points to this Dashboard. Set Custom Domain and Server Alias to the domain you want to use
then scroll down to the bottom of the page and (don't forget) to select the computer to provide the Frontend slave.
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
# 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 Secure Access entry shows the requested URL, the Frontend Slave is setup and working.
If you go to your requested URL (
master.slaptest.erp5.net) you can see that it points to the selected backend URL.