Commit Graph

63 Commits

Author SHA1 Message Date
dcce276b86 Rename script file 2020-04-08 10:05:43 +03:00
1b27e0f812 Make generate-jitsi-passwords.sh less magical 2020-04-08 10:05:10 +03:00
976ccf3880 Fix typo 2020-04-08 09:39:38 +03:00
f798605836 Undefine Jitsi secrets and require their (re-)definition 2020-04-08 09:37:54 +03:00
f9d39f1c0c update Jitsi, add generate-jitsi-passwords script 2020-04-08 02:07:52 +02:00
0ee2060c31 Reorganize paragraphs a bit 2020-04-05 10:03:51 +03:00
a04c67dbc4 Add information about rebuilding Jitsi Prosody configuration 2020-04-05 10:01:55 +03:00
d781c8fdf9 add optional Jitsi internal auth+guests docs
improve readability
2020-04-05 05:00:43 +02:00
067588b262 Upgrade riot-web 2020-03-30 16:54:18 +03:00
695d2c3ea5 Flip around Jitsi port format to match other ports
This matches the way the ports are written in prerequisites.md and is the format that UFW likes.
2020-03-27 23:33:38 -05:00
8ff55bcd14 Update documentation and changelog 2020-03-24 15:30:14 +02:00
d605b219a2 Manage Jitsi configuration by ourselves for most components
We do this for 2 reasons:

- so we can control things which are not controllable using environment
variables (for example `stunServers` in jitsi/web, since we don't wish
to use the hardcoded Google STUN servers if our own Coturn is enabled)

- so playbook variable changes will properly rebuild the configuration.
When using Jitsi environment variables, the configuration is only built
once (the first time) and never rebuilt again. This is not the
consistent with the rest of the playbook and with how Ansible operates.
We're not perfect at it (yet), because we still let the Jitsi containers
generate some files on their own, but we are closer and it should be
good enough for most things.

Related to  (Github Pull Request).
2020-03-24 09:35:21 +02:00
cdd9ee1962 Add Jitsi support 2020-03-23 17:19:15 +02:00