Installation & first steps

See the Administrator manual for system requirements and installation instructions.

Core: install custom images

Developers may prefer to run with one or more images from a development branch or alternative registries.

curl > 

See also module override.

The install script also accepts the following environment variables:

  • TESTING: override testing flag inside the default repository. It can be 0 (disabled) or 1 (enabled), default is 0
  • REPMOD: override default software repository URL, it could be something like https://mycustomrrepo.server.test/repomd
  • ADMIN_PASSWORD: override default admin password

Applications: install from CLI

Applications can be installed directly from the user interface.

If you prefer the command line, use the add-module command:

add-module <module> <node_id>

The above command will try to install the latest stable version of the module.

Example to install Dokuwiki on node 1:

add-module dokuwiki 1

You can also install an image which is not still available inside the repository by using its URL.

Example to install Dokuwiki directly from the image registry:

add-module 1

If the given image is already present in the local Podman storage, no remote download occurs and the local image is used instead. During development this might be unwanted and to work around this behavior execute the following command in every cluster node, before add-module:

podman rmi

Many applications need a configuration step after install, for more info, please refer to Administrator manual.

Module override

Sometimes you may need to install a specific tag for a module even from the UI. As an example, this can be usefull to override the image used by a user domain provider.

Command to override the Samba module:

redis-cli hset cluster/override/modules samba

You can now provision the user domain directly from the web interface.