matrix-docker-ansible-deploy/roles/matrix-server/templates/systemd/matrix-riot-web.service.j2

[Unit]
Description=Matrix Riot web server
After=docker.service
Requires=docker.service

[Service]
Type=simple
ExecStartPre=-/usr/bin/docker kill matrix-riot-web
ExecStartPre=-/usr/bin/docker rm matrix-riot-web
ExecStart=/usr/bin/docker run --rm --name matrix-riot-web \
			--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \
			-v {{ matrix_nginx_riot_web_data_path }}/config.json:/riot-web/webapp/config.json:ro \
			-v {{ matrix_nginx_riot_web_data_path }}/riot.im.conf:/data/riot.im.conf:ro \
			--network {{ matrix_docker_network }} \
			{% if not matrix_nginx_proxy_enabled %}
			-p 127.0.0.1:8765:8765 \
			{% endif %}
			{{ matrix_docker_image_riot }}
ExecStop=-/usr/bin/docker kill matrix-riot-web
ExecStop=-/usr/bin/docker rm matrix-riot-web
Restart=always
RestartSec=30

[Install]
WantedBy=multi-user.target
Initial commit 2017-07-31 22:07:30 +02:00			`[Unit]`
			`Description=Matrix Riot web server`
			`After=docker.service`
			`Requires=docker.service`

			`[Service]`
			`Type=simple`
			`ExecStartPre=-/usr/bin/docker kill matrix-riot-web`
			`ExecStartPre=-/usr/bin/docker rm matrix-riot-web`
			`ExecStart=/usr/bin/docker run --rm --name matrix-riot-web \`
Make the riot-web container run without root privileges 2018-05-14 13:31:43 +02:00			`--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \`
			`-v {{ matrix_nginx_riot_web_data_path }}/config.json:/riot-web/webapp/config.json:ro \`
			`-v {{ matrix_nginx_riot_web_data_path }}/riot.im.conf:/data/riot.im.conf:ro \`
Put all containers in their own isolated Docker network (matrix) Moving away from using the default bridge network to using our own. This isolates our services from other Docker containers running on the default network on the same host. The benefits are that: - isolation is a little better - we no longer share a default bridge network with any other containers that might be running on the host - there are no longer hard dependencies - we do service discovery by DNS name, and not via explicit `--link` usage during container start, so containers can start out of order and fail without bringing down others with them (`matrix-nginx-proxy` can continue running, even if one of the other services dies) In the future, when other services get introduced, the increased resilience and simplicity will help as well. 2018-08-08 07:23:36 +02:00			`--network {{ matrix_docker_network }} \`
Add support for not taking over a server (no matrix-nginx-proxy) and disabling Riot 2017-09-12 11:41:44 +02:00			`{% if not matrix_nginx_proxy_enabled %}`
			`-p 127.0.0.1:8765:8765 \`
			`{% endif %}`
Rename a bunch of playbook variables for better consistency 2018-08-08 08:17:18 +02:00			`{{ matrix_docker_image_riot }}`
Initial commit 2017-07-31 22:07:30 +02:00			`ExecStop=-/usr/bin/docker kill matrix-riot-web`
			`ExecStop=-/usr/bin/docker rm matrix-riot-web`
			`Restart=always`
			`RestartSec=30`

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