* 9bc262a4 prosody: fix building unstable images
* 0cbe0d98 web: add a env variable to enable/disable deep linking
* b22421b1 misc: publish nightly unstable images
* 78699fe6 web: allow to configure shard name using env variable
* a6853ef5 jvb: add octo configuration options
* d6fac8e0 jicofo: disable octo by default
* 1fa50485 doc: add link to Kubernetes setup
* e1cebcc2 web,jvb: add ability to disable web sockets for colibri
* 6c4dce16 jicofo: fix ENABLE_SCTP type
* 953a4d24 jicofo: use a client proxy connection
* d27336be web: always try to renew cert on container boot
* 73acbade web: remove deprecated config option
* cb4d9413 web: removed duplicate host headers
* ec570bae k8s: fix PodSecurityPolicy
* c4fc3d37 web: make a custom interface config possible
* b45b5059 web: always install acme.sh when container starts
* 94ca16d6 etherpad: remove quotes from all env vars
* c89ccc97 jicofo: reintroduce shibboleth auth
* a6486b45 examples: update traefik v2 example
* f4ec0232 misc: working on latest

The fallback is to use SCTP datachannels. This is not recomended.

acme.sh is smart enough to not send the request out unless it's necessary.

Fixes: https://github.com/jitsi/docker-jitsi-meet/issues/568

The previous version only installed acme.sh if it was not previously
installed. However, the check for a previous installation was based on
the existence of /config/acme.sh/acme.sh which is in the
external/persisted storage. The result was that acme.sh installation
would be skipped even for a new build of the web container if the
installation had been run on any previous build of the container. When
the web container is rebuilt, such as during an upgrade to a new stable
version, the new container would lack the cron job needed to
automatically updated the TLS certificates. Additionally, the version of
acme.sh installed in /config/acme.sh would never update even if the
pinned version in the Dockerfile was changed.

This patch sets the init script to always re-install acme.sh on
container start. The cron job installation from acme.sh is guarded by a
check for an existing job so there is no duplication. Re-installing also
has the effect of replacing the persisted /config/acme.sh/acme.sh with
the latest version set in the Dockerfile during upgrades.

Fixes #956

* a698da58 misc: add jicofo reservation env variables to compose
* 86c30225 web: brandingDataUrl -> dynamicBrandingUrl
* 88e950dc jicofo: fix healthcheck
* 493cbdd4 misc: fix typo
* e12d7f2b web : Add DESKTOP_SHARING_FRAMERATE_MIN and MAX env vars
* fa98a312 examples: fix k8s example
* 88d1034e doc: add port to PUBLIC_URL
* c876b40c doc: update CHANGELOG
* 5cf14b05 misc: working on latest

Fixes: #929

Fixes #931

* e28d0197 misc: working on latest

* 3e04fb4f prosody: fix lobby when authentication is enabled
* 24781e38 misc: working on latest

* 3ac53973 misc: working on latest