matrix-docker-ansible-deploy/roles/matrix-mxisd/templates/systemd/matrix-mxisd.service.j2

[Unit]
Description=Matrix mxisd Identity server
{% for service in matrix_mxisd_systemd_required_services_list %}
Requires={{ service }}
After={{ service }}
{% endfor %}
{% for service in matrix_mxisd_systemd_wanted_services_list %}
Wants={{ service }}
{% endfor %}

[Service]
Type=simple
ExecStartPre=-/usr/bin/docker kill matrix-mxisd
ExecStartPre=-/usr/bin/docker rm matrix-mxisd
ExecStart=/usr/bin/docker run --rm --name matrix-mxisd \
			--log-driver=none \
			--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \
			--network={{ matrix_docker_network }} \
			{% if matrix_mxisd_container_expose_port %}
			-p 127.0.0.1:8090:8090 \
			{% endif %}
			-v {{ matrix_mxisd_config_path }}:/etc/mxisd:ro \
			-v {{ matrix_mxisd_data_path }}:/var/mxisd \
			{{ matrix_mxisd_docker_image }}
ExecStop=-/usr/bin/docker kill matrix-mxisd
ExecStop=-/usr/bin/docker rm matrix-mxisd
Restart=always
RestartSec=30

[Install]
WantedBy=multi-user.target
Add mxisd Identity Server support 6 years ago			`[Unit]`
Make roles more independent of one another With this change, the following roles are now only dependent on the minimal `matrix-base` role: - `matrix-corporal` - `matrix-coturn` - `matrix-mailer` - `matrix-mxisd` - `matrix-postgres` - `matrix-riot-web` - `matrix-synapse` The `matrix-nginx-proxy` role still does too much and remains dependent on the others. Wiring up the various (now-independent) roles happens via a glue variables file (`group_vars/matrix-servers`). It's triggered for all hosts in the `matrix-servers` group. According to Ansible's rules of priority, we have the following chain of inclusion/overriding now: - role defaults (mostly empty or good for independent usage) - playbook glue variables (`group_vars/matrix-servers`) - inventory host variables (`inventory/host_vars/matrix.<your-domain>`) All roles default to enabling their main component (e.g. `matrix_mxisd_enabled: true`, `matrix_riot_web_enabled: true`). Reasoning: if a role is included in a playbook (especially separately, in another playbook), it should "work" by default. Our playbook disables some of those if they are not generally useful (e.g. `matrix_corporal_enabled: false`). 6 years ago			`Description=Matrix mxisd Identity server`
			`{% for service in matrix_mxisd_systemd_required_services_list %}`
			`Requires={{ service }}`
			`After={{ service }}`
			`{% endfor %}`
			`{% for service in matrix_mxisd_systemd_wanted_services_list %}`
			`Wants={{ service }}`
			`{% endfor %}`
Add mxisd Identity Server support 6 years ago
			`[Service]`
			`Type=simple`
			`ExecStartPre=-/usr/bin/docker kill matrix-mxisd`
			`ExecStartPre=-/usr/bin/docker rm matrix-mxisd`
			`ExecStart=/usr/bin/docker run --rm --name matrix-mxisd \`
Disable Docker container logging `--log-driver=none` is used for all Docker containers now. All these containers are started through systemd anyway and get logged in journald, so there's no need for Docker to be logging the same thing using the default `json-file` driver. Doing that was growing `/var/lib/docker/containers/..` infinitely until service/container restart. As a result of this, things like `docker logs matrix-synapse` won't work anymore. `journalctl -u matrix-synapse` is how one can see the logs. 6 years ago			`--log-driver=none \`
Add mxisd Identity Server support 6 years ago			`--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \`
			`--network={{ matrix_docker_network }} \`
Split playbook into multiple roles As suggested in #63 (Github issue), splitting the playbook's logic into multiple roles will be beneficial for maintainability. This patch realizes this split. Still, some components affect others, so the roles are not really independent of one another. For example: - disabling mxisd (`matrix_mxisd_enabled: false`), causes Synapse and riot-web to reconfigure themselves with other (public) Identity servers. - enabling matrix-corporal (`matrix_corporal_enabled: true`) affects how reverse-proxying (by `matrix-nginx-proxy`) is done, in order to put matrix-corporal's gateway server in front of Synapse We may be able to move away from such dependencies in the future, at the expense of a more complicated manual configuration, but it's probably not worth sacrificing the convenience we have now. As part of this work, the way we do "start components" has been redone now to use a loop, as suggested in #65 (Github issue). This should make restarting faster and more reliable. 6 years ago			`{% if matrix_mxisd_container_expose_port %}`
Add mxisd Identity Server support 6 years ago			`-p 127.0.0.1:8090:8090 \`
			`{% endif %}`
			`-v {{ matrix_mxisd_config_path }}:/etc/mxisd:ro \`
			`-v {{ matrix_mxisd_data_path }}:/var/mxisd \`
Rename playbook variables so they are consistently prefixed Pretty much all variables live in their own `matrix_<whatever>` prefix now and are grouped closer together in the default variables file (`roles/matrix-server/defaults/main.yml`). 6 years ago			`{{ matrix_mxisd_docker_image }}`
Add mxisd Identity Server support 6 years ago			`ExecStop=-/usr/bin/docker kill matrix-mxisd`
			`ExecStop=-/usr/bin/docker rm matrix-mxisd`
			`Restart=always`
			`RestartSec=30`

			`[Install]`
			`WantedBy=multi-user.target`