Browse Source

Upgrade Jitsi (v8960-2 -> v8960-3) and pass jitsi_user_username explicitly

It would work even without explicitly passing `jitsi_user_username` as
auto-detection logic will run. Passing it explicitly spares the Jitsi
role some work.

Related to:

- https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/pull/2
- https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2974#issuecomment-1784256903
pull/2948/head
Slavi Pantaleev 2 years ago
parent
commit
670ae6f602
2 changed files with 3 additions and 1 deletions
  1. +2
    -0
      group_vars/matrix_servers
  2. +1
    -1
      requirements.yml

+ 2
- 0
group_vars/matrix_servers View File

@@ -2491,6 +2491,8 @@ jitsi_base_path: "{{ matrix_base_data_path }}/jitsi"
jitsi_uid: "{{ matrix_user_uid }}"
jitsi_gid: "{{ matrix_user_gid }}"

jitsi_user_username: "{{ matrix_user_username }}"

# Normally, matrix-nginx-proxy is enabled and nginx can reach jitsi/web over the container network.
# If matrix-nginx-proxy is not enabled, or you otherwise have a need for it, you can expose
# the Jitsi HTTP port to the local host.


+ 1
- 1
requirements.yml View File

@@ -37,7 +37,7 @@
- src: git+https://gitlab.com/etke.cc/roles/grafana.git
version: v10.2.0-0
- src: git+https://github.com/mother-of-all-self-hosting/ansible-role-jitsi.git
version: v8960-2
version: v8960-3
name: jitsi
- src: git+https://gitlab.com/etke.cc/roles/ntfy.git
version: v2.7.0-2


Loading…
Cancel
Save