10 Commits (ee707a2c734d51de32bdadc76f8877006dcb7f92)

Author	SHA1	Message	Date
Samuel Meenzen	837cca4ee1	Move sliding sync url logic out of matrix-client.j2	10 months ago
Samuel Meenzen	9faa65f059	Advertise sliding-sync support when using conduit ... Starting from version `0.6.0` conduit natively supports some sync v3 (sliding-sync) features. https://gitlab.com/famedly/conduit/-/releases/v0.6.0 https://gitlab.com/famedly/conduit/-/merge_requests/501	10 months ago
Slavi Pantaleev	ae12ab5c24	Rename variable (matrix_client_element_jitsi_preferredDomain -> matrix_client_element_jitsi_preferredDomain)	10 months ago
Slavi Pantaleev	6d9a990657	Partially revert (preferredDomain -> preferred_domain) renaming ... Partially reverts 0a6b934a44. `preferred_domain` is only used by Element and does not apply to the `/.well-known/matrix/client` file.	10 months ago
Slavi Pantaleev	0a6b934a44	Rename Element configuration key (preferredDomain -> preferred_domain) ... Related to: https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2375#issuecomment-1655758296	10 months ago
Slavi Pantaleev	023fe3ea08	Add sliding-sync support ... This allows people to try out the new Element X clients, which need to run against the sliding-sync proxy (https://github.com/matrix-org/sliding-sync). Supersedes https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2515 The code is based on the existing PR (#2515), but heavily reworked. Major changes: - lots of internal refactoring and variable renaming - fixed self-building to support non-amd64 architectures - changed to talk to the homeserver locally, over the container network (not publicly) - no more matrix-nginx-proxy support due to complexity (see below) - no more `matrix_server_fqn_sliding_sync_proxy` in favor of `matrix_sliding_sync_hostname` and `matrix_sliding_sync_path_prefix` - runs on `matrix.DOMAIN/sliding-sync` by default, so it can tried easily without having to create new DNS records	1 year ago
td	af10d350bc	fix: missing endif in client well-known	1 year ago
Jayesh Nirve	6939a3d6d3	fix: only add element related entries to client well-known if element is enabled (#2453) ... * fix: only add element related entries to client well-known if element is enabled * Fix matrix-base/defaults/main.yml syntax --------- Co-authored-by: Slavi Pantaleev <slavi@devture.com>	1 year ago
NullIsNot0	77451c6a71	Enable location sharing in Element (#2276) ... * Enable location sharing in Element * Update roles/custom/matrix-client-element/tasks/validate_config.yml Co-authored-by: Slavi Pantaleev <slavi@devture.com> * Update roles/custom/matrix-client-element/tasks/setup_install.yml Co-authored-by: Slavi Pantaleev <slavi@devture.com> * Rename location sharing vars to be consistent with other vars * Rename style.json to map_style.json * Add m.tile_server section to /.well-known/matrix/client Co-authored-by: Slavi Pantaleev <slavi@devture.com>	2 years ago
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.	2 years ago