The container will refuse to start and provide some useful information
to the user:
```
docker-jitsi-meet-jibri-1 | cap[cap_sys_admin] not permitted
docker-jitsi-meet-jibri-1 | Required capability SYS_ADMIN is missing
docker-jitsi-meet-jibri-1 | [cont-init.d] 10-config: exited 1.
docker-jitsi-meet-jibri-1 | [cont-finish.d] executing container finish scripts...
docker-jitsi-meet-jibri-1 | [cont-finish.d] done.
docker-jitsi-meet-jibri-1 | [s6-finish] waiting for services.
```
This is the place listed on
https://googlechromelabs.github.io/chrome-for-testing/
which would seem to be the least likely to silently break.
Currently, the edgedl.me.gvt1.com location is broken.
Signed-off-by: Kurt Garloff <kurt@garloff.de>
If the container was staryed without a /dev/shm of at least 2GB
(defaults to 6MB in Docker) Chrome will behave erratically or crash.
Catch this with a tiny binary and make the container fail to start.
Ref: https://github.com/jitsi/docker-jitsi-meet/issues/1653
Introduce a few new environment variables:
- `JIBRI_RECORDING_VIDEO_ENCODE_PRESET`
- `JIBRI_RECORDING_CONSTANT_RATE_FACTOR`
- `JIBRI_RECORDING_CONSTANT_FRAMERATE`
- `JIBRI_RECORDING_CONSTANT_QUEUE_SIZE`
- `JIBRI_RECORDING_CONSTANT_STREAMING_MAX_BITRATE`
Co-authored-by: Christian Ribeaud <christian.ribeaud@karakun.com>
Use default values everywhere so they don't need to be specified in the
.env file.
This makes the default .env file much smaller (the larger config options
are documented in the handbook) and should make it easier to port the
setup to runtimes other than Docker Compose.
* jicofo: add optional XMPP_PORT value
* include compose and env example for XMPP_PORT
* extends use of the XMPP_PORT property
* fix compose to use default
* re-commenting XMPP_PORT value
* include XMPP_PORT in compose for all services
* always use $XMPP_PORT, value defaulted in template
* missing JVB setting