matrix-docker-ansible-deploy/roles/matrix-postgres/templates/usr-local-bin/matrix-postgres-cli.j2

#jinja2: lstrip_blocks: "True"
#!/bin/bash

docker run \
	-it \
	--rm \
	--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \
    --cap-drop=ALL \
	--env-file={{ matrix_postgres_base_path }}/env-postgres-psql \
	--network {{ matrix_docker_network }} \
	{{ matrix_postgres_docker_image_to_use }} \
	psql -h {{ matrix_postgres_connection_hostname }}
Fix indentation in templates Use Jinja2 lstrip_blocks option in templates to ensure consistent indentation in generated files. 2019-05-07 19:23:35 +00:00			`#jinja2: lstrip_blocks: "True"`
Initial commit 2017-07-31 20:07:30 +00:00			`#!/bin/bash`

Do not leave containers behind after matrix-postgres-cli usage 2017-09-08 11:18:12 +00:00			`docker run \`
			`-it \`
			`--rm \`
Drop capabilities in a few more places Continuation of 316d653d3e0530 2019-01-28 09:43:32 +00:00			`--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \`
			`--cap-drop=ALL \`
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. 2019-01-12 15:53:00 +00:00			`--env-file={{ matrix_postgres_base_path }}/env-postgres-psql \`
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 05:23:36 +00:00			`--network {{ matrix_docker_network }} \`
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`). 2018-11-01 06:46:47 +00:00			`{{ matrix_postgres_docker_image_to_use }} \`
Rename a bunch of playbook variables for better consistency 2018-08-08 06:17:18 +00:00			`psql -h {{ matrix_postgres_connection_hostname }}`