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

#!/bin/bash

docker run \
	-it \
	--rm \
	--env-file={{ matrix_environment_variables_data_path }}/env-postgres-pgsql-docker \
	--network {{ matrix_docker_network }} \
	{{ docker_postgres_image_to_use }} \
	psql -h {{ matrix_postgres_connection_hostname }}
Initial commit 2017-07-31 22:07:30 +02:00			`#!/bin/bash`

Do not leave containers behind after matrix-postgres-cli usage 2017-09-08 13:18:12 +02:00			`docker run \`
			`-it \`
			`--rm \`
			`--env-file={{ matrix_environment_variables_data_path }}/env-postgres-pgsql-docker \`
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 }} \`
Use Postgres 10.x by default (only for new installs) This playbook just tries to avoid trying to setup a Postgres 10 database with existing 9.x files, as that makes Postgres complain. Due to this, existing installs (still on 9.x) are detected and left on Postgres 9.x. They need to be upgraded to Postgres 10.x manually. 2018-05-28 13:47:09 +02:00			`{{ docker_postgres_image_to_use }} \`
Add support for using an external PostgreSQL server 2017-09-08 15:53:24 +02:00			`psql -h {{ matrix_postgres_connection_hostname }}`