forked from udima-university/ansible-jitsi-meet
-
Notifications
You must be signed in to change notification settings - Fork 0
/
hosts
25 lines (21 loc) · 1.26 KB
/
hosts
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
## from here we are controlling the setup on which server to install.
## central: jitsi-meet, prosody, jicofo
## ONLY one host should be in this group
## The name jitsi-meet is then what shows up when you run the playbook.
## note that mydomain.com must be same as hosts_vars/mydomain.com directory name else error
[central]
mydomain.com ansible_host=1.2.3.4 ansible_ssh_private_key_file=path_to_ssh_key ansible_python_interpreter=/usr/bin/python3
## videobridge: jitsi-videobridge2
## here install videobridge on same server as jitsi-meet if ansible_host is same as in central group
[videobridges]
jvb1.mydomain.com ansible_host=1.2.3.4 ansible_ssh_private_key_file=path_to_ssh_key ansible_python_interpreter=/usr/bin/python3
#jvb2.mydomain.com ansible_host=1.2.3.4 ansible_ssh_private_key_file=path_to_ssh_key ansible_python_interpreter=/usr/bin/python3
## here install jibri on same server as jitsi-meet if ansible_host is same as in central group
[jibris]
jibri1.mydomain.com ansible_host=1.2.3.4 ansible_ssh_private_key_file=path_to_ssh_key ansible_python_interpreter=/usr/bin/python3
#jibri2.mydomain.com ansible_host=1.2.3.4 ansible_ssh_private_key_file=path_to_ssh_key ansible_python_interpreter=/usr/bin/python3
# No need to edit this
[meet:children]
central
videobridges
jibris