SlapOS is a decentralized Cloud Computing technology that can automate the deployment and configuration of applications in a heterogeneous environment.


  • Supply And Request Slapos Master
  • Wait for Deployment
  • Request Frontend
  • Verification

This tutorial will guide you through the steps of installing and configuring a SlapOS Master to manage a network of computers. It will use the single line installer (for other ways, see experimental ways to install SlapOS Master). Once completed you will have a COMP-ROOT node similar to that of, Nexedi's cloud hosting provider, which can then be used as starting point for creating a network of nodes to provide software instances.

Before starting this tutorial, make sure you have read the SlapOS architecture and SlapOS system requirements in order to make yourself familiar with the terminology and overall concepts.

For completing this tutorial, it is required to have a fresh server (Debian 9 or 10) with command line access and wget installed. The tutorial will use an arbitrary server from a cloud provider such as OVH or

Note, that Debian 9 and 10 are tested daily and can be installed from binary cache, meaning installation will take between 15-30 mins depending on the machine. Other Linux distributions are also supported by the single line installer, but source code may have to be compiled from scratch meaning installation will take around 8-9 hours.

Installing SlapOS Master

The currently recommended way of installing a SlapOS Master is using the single line installer.

Verify Debian Version

debian@slapostest:~$ lsb_release -a
No LSB modules are available.
Distributor ID:    Debian
Description:    Debian GNU/Linux 10 (buster)
Release:    10
Codename:    buster

Start by ssh-ing into your server and verifying the Debian version using:

lsb_release -a

Call Single Line Installer

sudo su
# wget
# bash slapos-master-standalone

Change to root user and call the single line installer.

This will download, build and install the required packages (ansible, slapos-node, slapos-proxy), configure the computer as a SlapOS standalone node, and deploy SlapOS Master (ERP5) and a Frontend (Apache) service inside. Note, that, as mentioned, in case the required files are not available from binary cache, compilation may take several hours.

Check Compilation Status

TASK [standalone-shared : Check ERP5 state] ************************************
fatal: []: FAILED! => {
  "changed": true,
  "cmd": "/usr/local/bin/erp5-show -s",
  "delta": "0:00:00.059622",
  "end": "2018-03-02 10:08:44.316161",
  "failed": true,
  "rc": 2,
  "start": "2018-03-02 10:08:44.256539",
  "stderr": "",
  "stdout": "Your software is still building, be patient it can take a while",
  "stdout_lines": ["Your software is still building, be patient it can take a while"],
  "warnings": []

Once the loader finishes its first run it can fail with the above message.

This is expected while the software is compiling!. You can rerun the script above or check the status of the installation directly by calling:

erp5-show -s

Verify Successful Installation

# erp5-show -s
Build successful, connect to:
username: zope  password: [xxx-password-xxx]

Once installation has successfully completed, the status message will be similar to the one displayed above. It means the SlapOS Master is ready to be configured.

Run the bash script one final time to check there were no errors,

root@localhost:/home/debian# bash slapos-master-standalone
PLAY RECAP *********************************************************************                  : ok=56   changed=15   unreachable=0   failed=0

Note down the url provided along with the username and password.

Access SlapOS Master ERP5 Interface

ERP5 Interface - Login Screen

Start by going to the URL (https://[IPv4]) provided in the past tutorial and append "/erp5/" to the URL which will take you to directly to the ERP5 interface. Login with the username and password you have received when the installation of the Master finished.

Next: Configure SlapOS Master

How To Configure SlapOS Master