* Add docs/just.md as dedicated documentation of "just" commands
This is partially based on fb60ba67f6
(announcement of adoption of "just" program). It also refers descriptions on installing.md.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Create a table for examples
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Fix entries on the table
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Move the anchor link to "agru"
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Edit docs/faq.md: add an entry for the just
It is based on the existing explanation of the just on docs/maintenance-upgrading-services.md.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Add links to docs/just.md
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Update docs/just.md: add a common note
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Clarify "What is just" section on FAQ
* Update just.md
* Mention install-service
---------
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
Co-authored-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
Co-authored-by: Slavi Pantaleev <slavi@devture.com>
2.9 KiB
Upgrading the Matrix services
This playbook not only installs the various Matrix services for you, but can also upgrade them as new versions are made available.
While this playbook helps you to set up Matrix services and maintain them, it will not automatically run the maintenance task for you. You will need to update the playbook and re-run it manually.
The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities (for example, see here for known ones on Element Web).
Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date.
The developers of this playbook strive to maintain the playbook updated, so that you can re-run the playbook to address such vulnerabilities. It is your responsibility to keep your server and the services on it up-to-date.
If you want to be notified when new versions of Synapse are released, you should join the Synapse Homeowners room: #homeowners:matrix.org.
Steps to upgrade the Matrix services
Before updating the playbook and the Ansible roles in the playbook, take a look at the changelog to see if there have been any backward-incompatible changes that you need to take care of.
If it looks good to you, go to the matrix-docker-ansible-deploy
directory, then:
-
update your playbook directory and all upstream Ansible roles (defined in the
requirements.yml
file) using:- either:
just update
- or: a combination of
git pull
andjust roles
(ormake roles
if you havemake
program on your computer instead ofjust
)
If you don't have either
just
tool ormake
program, you can run theansible-galaxy
tool directly:rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force
For details about
just
commands, take a look at: Runningjust
commands. - either:
-
re-run the playbook setup and restart all services:
ansible-playbook -i inventory/hosts setup.yml --tags=install-all,start
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 is to run the just
"recipe": just install-all
or just setup-all
.
Note: major version upgrades to the internal PostgreSQL database are not done automatically. To upgrade it, refer to the upgrading PostgreSQL guide.