matrix-docker-ansible-deploy/roles/custom/matrix-base/tasks/setup_matrix_base.yml

---

- name: Ensure Matrix base path exists
  ansible.builtin.file:
    path: "{{ item }}"
    state: directory
    mode: "{{ matrix_base_data_path_mode }}"
    owner: "{{ matrix_user_username }}"
    group: "{{ matrix_user_groupname }}"
  with_items:
    - "{{ matrix_base_data_path }}"

- name: Ensure Matrix network is created in Docker
  community.docker.docker_network:
    name: "{{ matrix_docker_network }}"
    driver: bridge

- name: Ensure matrix-remove-all script created
  ansible.builtin.template:
    src: "{{ role_path }}/templates/usr-local-bin/matrix-remove-all.j2"
    dest: "{{ matrix_local_bin_path }}/matrix-remove-all"
    mode: 0750
Initial commit 2017-07-31 22:07:30 +02:00			`---`

Move SSL certificates from /etc/pki/acmetool-certs to /matrix/ssl Moving keeps everything in the /matrix directory, so that we wouldn't contaminate anything else on the system or risk clashing with something else. Also retrieving certificates separately for the Riot and Matrix domains, which should help in multiple ways: - allows them to be very different (completely separate base domain..) - allows for Riot to be disabled for the playbook some time later and still have the code not break 2017-09-11 22:50:14 +02:00			`- name: Ensure Matrix base path exists`
Use fully-qualified module names for builtin Ansible modules Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1939 2022-07-18 09:39:08 +02:00			`ansible.builtin.file:`
Move SSL certificates from /etc/pki/acmetool-certs to /matrix/ssl Moving keeps everything in the /matrix directory, so that we wouldn't contaminate anything else on the system or risk clashing with something else. Also retrieving certificates separately for the Riot and Matrix domains, which should help in multiple ways: - allows them to be very different (completely separate base domain..) - allows for Riot to be disabled for the playbook some time later and still have the code not break 2017-09-11 22:50:14 +02:00			`path: "{{ item }}"`
			`state: directory`
Make the mode of the base path configurable 2019-01-14 14:28:37 +01:00			`mode: "{{ matrix_base_data_path_mode }}"`
Move SSL certificates from /etc/pki/acmetool-certs to /matrix/ssl Moving keeps everything in the /matrix directory, so that we wouldn't contaminate anything else on the system or risk clashing with something else. Also retrieving certificates separately for the Riot and Matrix domains, which should help in multiple ways: - allows them to be very different (completely separate base domain..) - allows for Riot to be disabled for the playbook some time later and still have the code not break 2017-09-11 22:50:14 +02:00			`owner: "{{ matrix_user_username }}"`
Allow the matrix user username and groupname to be configured separately No migration steps should be required. 2020-05-01 19:59:32 +02:00			`group: "{{ matrix_user_groupname }}"`
Move SSL certificates from /etc/pki/acmetool-certs to /matrix/ssl Moving keeps everything in the /matrix directory, so that we wouldn't contaminate anything else on the system or risk clashing with something else. Also retrieving certificates separately for the Riot and Matrix domains, which should help in multiple ways: - allows them to be very different (completely separate base domain..) - allows for Riot to be disabled for the playbook some time later and still have the code not break 2017-09-11 22:50:14 +02:00			`with_items:`
Make /matrix owned by matrix:matrix 2017-10-24 06:01:11 +02:00			`- "{{ matrix_base_data_path }}"`
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
Revert "Work around buggy docker_network sometimes failing to work" The docker_network bug was fixed two years ago This reverts commit 36658addcd688074eb9062ee71f16ed8a0bcad1b. 2020-08-02 20:54:13 +02:00			`- name: Ensure Matrix network is created in Docker`
use fqcns for some task Signed-off-by: Sebastian Gumprich <github@gumpri.ch> 2022-10-28 13:20:17 +02:00			`community.docker.docker_network:`
Revert "Work around buggy docker_network sometimes failing to work" The docker_network bug was fixed two years ago This reverts commit 36658addcd688074eb9062ee71f16ed8a0bcad1b. 2020-08-02 20:54:13 +02:00			`name: "{{ matrix_docker_network }}"`
			`driver: bridge`
add script + doc to remove everything 2018-11-28 11:02:51 +01:00
			`- name: Ensure matrix-remove-all script created`
Use fully-qualified module names for builtin Ansible modules Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1939 2022-07-18 09:39:08 +02:00			`ansible.builtin.template:`
add script + doc to remove everything 2018-11-28 11:02:51 +01:00			`src: "{{ role_path }}/templates/usr-local-bin/matrix-remove-all.j2"`
Made directory variables for /etc/systemd/system , /etc/cron.d , /usr/local/bin 2020-03-24 19:27:58 +01:00			`dest: "{{ matrix_local_bin_path }}/matrix-remove-all"`
add script + doc to remove everything 2018-11-28 11:02:51 +01:00			`mode: 0750`