App installation¶
In addition to manual guides in the Uberspace Lab we also provide a command to install applications automatically:
[isabell@stardust ~]$ uberspace lab install wordpress
[...]
This will load an Ansible playbook from the public Lab repository and start it with default configurations. You will be asked to confirm the configuration before actually running any installations.
Dry run installation¶
You can use --dry to just check the installation first without changing anything on your Asteroid:
[isabell@stardust ~]$ uberspace lab install wordpress
[...]
This will enable ansible check-mode and show what tasks would be changed when running without --dry,
some tasks will be skipped as they cannot be executed in check-mode.
Custom configuration¶
Similar to the guides, the default configurations of the playbooks assume a fresh Asteroid without any other apps running and by using the default domains, mailaddresses etc.
You can change configurations with multiple usage of --var config=value. For example:
[isabell@stardust ~]$ uberspace lab install wordpress --var domain=example.com --var installation_path=~/www/example.com
[...]
Wordpress
| installation_path: /home/isabell/www/example.com
| db_name: isabell_wordpress
| title: isabell's new Website
| domain: example.com
| admin_username: dummy
| admin_mailaddress: sysmail@isabell.uber.space
| admin_password: RANDOM
[...]
Logging¶
The command creates a data directory in ~/.config/uberspace/app_playbooks where the playbook and all information about the installation are stored.
Have a look at the ansible-runner documentation
for more information about the structure and contents of that directory.
Install custom playbooks¶
Instead of a simple application name you can also provide a URL or local path to execute custom playbooks:
[isabell@stardust ~]$ uberspace lab install https://example.com/playbook.yaml
[...]
[isabell@stardust ~]$ uberspace lab install ~/playbook.yaml
[...]