The goal of this tutorial is to teach how to install
what we call Software Release, here Wordpress Software Release.
In SlapOS, it will allow you
to make deployment of Wordpress instances available.
Basic software concepts of SlapOS
In SlapOS, software is divided in two parts. Those concepts will be used during all the SlapOS tutorials, so be sure to read them carefully.
First is the Software Release. It
represents the entire installation of a software, but without configuration files. At this point, software is not usable, because there is no configuration file, i.e Wordpress and dependencies is installed but no disk image or specific configuration exists yet.
Then comes the Software Instance. It will reuse installed Software Release by creating wrappers, configuration files and anything specific to an instance. In the case of Wordpress, it will create a disk image with possibly data in it, and some configuration files.
When a Software Release is installed on a machine, SlapOS can then
create Software Instances using the Software Release and only
creating what is needed : configuration file, and disk image.
This way, you will have one Wordpress installation (the Wordpress Software Release), and multiple running instances of Wordpress (Wordpress Software Instances) using the same Wordpress installation,
allowing you to save space and not reinstalling Wordpress each time a new instance gets deployed.
In the previous tutorial, you set up a SlapOS node, also known internally as Computer. A Computer is divided into Computer Partitions. You set up the number of those partitions in the slapos.cfg configuration file, remember? 20 partitions means that 20 different Software Instance can be deployed on your node. If you installed the Wordpress Software Release on your node, it means that 20 Wordpress Software Instances can be installed on your node. If you installed the Wordpress Software Release AND the MySQL Software Release on your node, it means that 20 Software Instance of Wordpress or MySQL can be installed on your node.
Workflow of a Software Instance
Currently, when you request a Software Instance, the SlapOS Master will redirect you to the order page. After a few seconds, the instance document will appear. It will be by default in "Looking for free partition" state. When the SlapOS Master finds a suitable computer to host the instance, status will change to "Waiting for partition instantiation". When the computer is actually deploying the instance, it will change to "Start in progress", then "Started" when it has finished and checked that service is up.
You can stop your instance, changing instance state to "Stop in progress", then "Stopped". You can also destroy it (forever!), changing state to "Destroy in progress", then "Destroyed".
Why my new Software Instance keeps being in "Looking for free partition" state?
A newly requested instance staying in "Looking for free partition" state too long means that no suitable computer has been found by the SlapOS Master. If you specified your computer as a target, it means that either there is no more free Computer Partition (all are already taken), or that the linked Software Release is not correctly installed.
As a general convention, commands prepended with $ might be run as
ordinary user whereas commands prepended by # require