matrix-docker-ansible-deploy/docs/installing.md
Suguru Hirahara ea48e5e9eb
Create docs/playbook-tags.md: move explanation about playbook tags
The playbook tags are not limited to installation, and the explanation's detail makes the section worth being split to a dedicated individual page.

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
2024-11-09 03:28:45 +09:00

6.5 KiB
Raw Blame History

Installing

Quick start | Prerequisites > Configuring your DNS server > Getting the playbook > Configuring the playbook > Installing

If you've configured your DNS and have configured the playbook, you can start the installation procedure.

Before installing and each time you update the playbook in the future, you will need to update the Ansible roles in this playbook by running just roles. just roles is a shortcut (a roles target defined in justfile and executed by the just utility) which ultimately runs agru or ansible-galaxy (depending on what is available in your system) to download Ansible roles. If you don't have just, you can also manually run the roles commands seen in the justfile.

There's another shortcut (just update) which updates the playbook (git pull) and updates roles (just roles) at the same time.

Install Matrix

The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks.

The general command syntax for installation (and also maintenance) is: ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE. It is recommended to get yourself familiar with the playbook tags before proceeding.

If you don't use SSH keys for authentication, but rather a regular password, you may need to add --ask-pass to the all Ansible commands

If you do use SSH keys for authentication, and use a non-root user to become root (sudo), you may need to add -K (--ask-become-pass) to all Ansible commands

There 2 ways to start the installation process - depending on whether you're Installing a brand new server (without importing data) or Installing a server into which you'll import old data.

Installing a brand new server (without importing data)

If this is a brand new Matrix server and you won't be importing old data into it, run all these tags:

ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start

This will do a full installation and start all Matrix services.

Installing a server into which you'll import old data

If you will be importing data into your newly created Matrix server, install it, but do not start its services just yet. Starting its services or messing with its database now will affect your data import later on.

To do the installation without starting services, run ansible-playbook with the install-all tag only:

ansible-playbook -i inventory/hosts setup.yml --tags=install-all

Note: do not run the just "recipe" just install-all instead, because it automatically starts services at the end of execution.

When this command completes, services won't be running yet.

You can now:

.. and then proceed to starting all services:

ansible-playbook -i inventory/hosts setup.yml --tags=start

Finalize the installation

Now that services are running, you need to finalize the installation process (required for federation to work!) by Configuring Service Discovery via .well-known.

If you need the base domain for anything else (such as hosting a website), you have to configure it manually, following the procedure described on the linked documentation.

However, if you do not need the base domain (example.com) for anything else, the easiest way of configuring it is to serve the base domain from the integrated web server. It will enable you to use a Matrix user identifier like @<username>:example.com while hosting services on a subdomain like matrix.example.com.

To configure Service Discovery in this way, add the following configuration to your inventory/host_vars/matrix.example.com/vars.yml file:

matrix_static_files_container_labels_base_domain_enabled: true

After configuring the playbook, run the installation command: just install-all or just setup-all

Things to do next

After finilizing the installation, you can:

Maintaining your setup in the future

Feel free to re-run the setup command any time you think something is off with the server configuration. Ansible will take your configuration and update your server to match.

Note that if you remove components from vars.yml, or if we switch some component from being installed by default to not being installed by default anymore, you'd need to run the setup command with --tags=setup-all instead of --tags=install-all. See this page on the playbook tags for more information.

A way to invoke these ansible-playbook commands with less typing in the future is to use just to run them: just install-all or just setup-all. See our justfile for more information.