|
|
@ -51,11 +51,8 @@ A Jitsi Meet installation can be broken down into the following components: |
|
|
|
|
|
|
|
|
|
|
|
![](resources/docker-jitsi-meet.png) |
|
|
|
![](resources/docker-jitsi-meet.png) |
|
|
|
|
|
|
|
|
|
|
|
The diagram shows a typical deployment in a host running Docker, with a separate container |
|
|
|
The diagram shows a typical deployment in a host running Docker. This project |
|
|
|
(not included in this project) which acts as a reverse proxy and SSL terminator, then |
|
|
|
separates each of the components above into interlinked containers. To this end, |
|
|
|
passing the traffic to the web container serving Jitsi Meet. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This project separates each of the components above into interlinked containers. To this end, |
|
|
|
|
|
|
|
several container images are provided. |
|
|
|
several container images are provided. |
|
|
|
|
|
|
|
|
|
|
|
### Images |
|
|
|
### Images |
|
|
@ -91,6 +88,23 @@ Variable | Description | Example |
|
|
|
`HTTPS_PORT` | Exposed port for HTTPS traffic | 8443 |
|
|
|
`HTTPS_PORT` | Exposed port for HTTPS traffic | 8443 |
|
|
|
`DOCKER_HOST_ADDRESS` | IP address of the Docker host, needed for LAN environments | 192.168.1.1 |
|
|
|
`DOCKER_HOST_ADDRESS` | IP address of the Docker host, needed for LAN environments | 192.168.1.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
**NOTE**: The mobile apps won't work with self-signed certificates (the default) |
|
|
|
|
|
|
|
see below for instructions on how to obtain a proper certificate with Let's Encrypt. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### Let's Encrypt configuration |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you plan on exposing this container setup to the outside traffic directly and |
|
|
|
|
|
|
|
want a proper TLS certificate, you are in luck because Let's Encrypt support is |
|
|
|
|
|
|
|
built right in. Here are the required options: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Variable | Description | Example |
|
|
|
|
|
|
|
--- | --- | --- |
|
|
|
|
|
|
|
`ENABLE_LETSENCRYPT` | Enable Let's Encrypt certificate generation | 1 |
|
|
|
|
|
|
|
`LETSENCRYPT_DOMAIN` | Domain for which to generate the certificate | meet.example.com |
|
|
|
|
|
|
|
`LETSENCRYPT_EMAIL` | E-Mail for receiving important account notifications (mandatory) | alice@atlanta.net |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In addition, you will need to set `HTTP_PORT` to 80 and `HTTPS_PORT` to 443. |
|
|
|
|
|
|
|
|
|
|
|
### SIP gateway configuration |
|
|
|
### SIP gateway configuration |
|
|
|
|
|
|
|
|
|
|
|
If you want to enable the SIP gateway, these options are required: |
|
|
|
If you want to enable the SIP gateway, these options are required: |
|
|
@ -162,7 +176,6 @@ option. |
|
|
|
* Support multiple Jitsi Videobridge containers. |
|
|
|
* Support multiple Jitsi Videobridge containers. |
|
|
|
* Support container replicas (where applicable). |
|
|
|
* Support container replicas (where applicable). |
|
|
|
* Docker Swarm mode. |
|
|
|
* Docker Swarm mode. |
|
|
|
* Native Let's Encrypt support. |
|
|
|
|
|
|
|
* More services: |
|
|
|
* More services: |
|
|
|
* Jibri. |
|
|
|
* Jibri. |
|
|
|
* TURN server. |
|
|
|
* TURN server. |
|
|
|