4f0bed6998
We've been running into problems with Jitsi-Meet processes not restarting cleanly if we only docker-compose up after image pulls. Instead, check for whether the pull resulted in new image downloads and then cleanly down and up the containers, which seems to address the problem based on manual testing on the servers. Change-Id: Id551767e72102a4b8667aa9dacc81755f332a278 |
||
---|---|---|
.. | ||
main.yaml |