Aine
338e6d91c3
synapse-admin v0.10.3-etke16: Upgrade to react-admin v5, restrict actions on specific users ( #3543 )
...
* synapse-admin v0.10.3-etke15: Upgrade to react-admin v5
* v0.10.3-etke16
* fix linter
* add _auto and _custom vars
* Use 2 spaces before #noqa var-naming
---------
Co-authored-by: Slavi Pantaleev <slavi@devture.com>
2024-09-24 16:58:17 +03:00
Slavi Pantaleev
e000cbf0f4
Auto-configure synapse-admin to be restricted to a single homeserver (the one managed by the playbook)
2024-07-01 16:03:52 +03:00
Slavi Pantaleev
51df34e7ae
Ensure each container labels file defines at least one service
...
Most of these files were defining a service, usually toward the end.
These lines have been moved upward.
Some components (mautrix-signal, mautrix-gmessages, etc.) were defining
a service conditionally (only if metrics are exposed, etc). This was
causing issues like these in the Traefik logs:
> level=error msg="service \"matrix-mautrix-twitter\" error: port is missing" providerName=docker container=matrix-mautrix-twitter-..
2024-01-17 17:56:45 +02:00
Slavi Pantaleev
2511b34a7c
Stop containers gracefully, instead of outright killing them
2023-12-06 11:52:23 +02:00
Slavi Pantaleev
799cbb44fb
Add the ability to control (Traefik) routing priority for Element and synapse-admin
...
This may proof useful to someone in the future.
2023-02-14 09:04:50 +02:00
Slavi Pantaleev
c33ed94352
Add security headers to synapse-admin (on Traefik)
...
We've had it on `matrix-nginx-proxy` before, but
our initial support for Traefik did not include any of these security
headers.
2023-02-14 08:49:04 +02:00
Slavi Pantaleev
5ab5f28d14
Add support for running synapse-admin (on Traefik) at the root path
...
Previously, we had to run it at a subpath, like `/synapse-admin`.
We can now dedicate a whole domain and the `/` path to it, should we
wish to do so.
2023-02-14 08:42:50 +02:00
Slavi Pantaleev
3d9aa8387e
Add (native) Traefik support to synapse-admin
...
Previously, it had to go through matrix-nginx-proxy.
It's exposed to Traefik directly via container labels now.
2023-02-13 15:08:42 +02:00
Slavi Pantaleev
7086c0ebe3
matrix_host_command_sh -> devture_systemd_docker_base_host_command_sh (via com.devture.ansible.role.systemd_docker_base)
2022-11-04 16:40:25 +02:00
Slavi Pantaleev
a9a81460ec
matrix_host_command_docker -> devture_systemd_docker_base_host_command_docker (via com.devture.ansible.role.systemd_docker_base)
2022-11-04 16:39:35 +02:00
Slavi Pantaleev
f03f716989
matrix_systemd_unit_home_path -> devture_systemd_docker_base_systemd_unit_home_path (via com.devture.ansible.role.systemd_docker_base)
2022-11-04 16:37:47 +02:00
Slavi Pantaleev
410a915a8a
Move roles/matrix* to roles/custom/matrix*
...
This paves the way for installing other roles into `roles/galaxy` using `ansible-galaxy`,
similar to how it's done in:
- https://github.com/spantaleev/gitea-docker-ansible-deploy
- https://github.com/spantaleev/nextcloud-docker-ansible-deploy
In the near future, we'll be removing a lot of the shared role code from here
and using upstream roles for it. Some of the core `matrix-*` roles have
already been extracted out into other reusable roles:
- https://github.com/devture/com.devture.ansible.role.postgres
- https://github.com/devture/com.devture.ansible.role.systemd_docker_base
- https://github.com/devture/com.devture.ansible.role.timesync
- https://github.com/devture/com.devture.ansible.role.vars_preserver
- https://github.com/devture/com.devture.ansible.role.playbook_runtime_messages
- https://github.com/devture/com.devture.ansible.role.playbook_help
We just need to migrate to those.
2022-11-03 09:11:29 +02:00
