You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 17, 2024. It is now read-only.
Copy file name to clipboardexpand all lines: README.md
+6-10
Original file line number
Diff line number
Diff line change
@@ -31,11 +31,11 @@ When running the build version of the Phoenix app, you must specify the addresse
31
31
As well as the authentication token via the environment variables:
32
32
33
33
```sh
34
-
BE_JF_ADDRESSES=<IP_ADDRESS1>:<PORT1> OR <DOMAIN1><IP_ADDRESS2>:<PORT2> OR <DOMAIN2>#Example of using two fishjams: `127.0.0.1:5002 room.fishjam.ovh`, if not provided in dev environment `localhost:5002 localhost:5003` is used.
34
+
BE_JF_ADDRESS=<IP_ADDRESS>:<PORT1> OR <DOMAIN1>#Example `127.0.0.1:5002 OR room.fishjam.ovh`, if not provided in dev environment `localhost:5002` is used.
35
35
BE_JF_SERVER_API_TOKEN=<TOKEN>#This must be the same token that was setup in fishjam. In `docker-compose-dev.yaml` we setup `development` and this variable is used by default in `dev` environment
36
36
```
37
37
38
-
Optionally, in production, these variables can be set:
38
+
Optionally, in production, these variables can be set:
39
39
*`BE_PEER_JOIN_TIMEOUT` - can be used to limit the period in which a new peer must join the meeting,
40
40
*`BE_JF_SECURE_CONNECTION` - enforces connecting the backend to fishjam through `wss` protocol,
41
41
*`BE_HOST` - address of backend
@@ -57,21 +57,17 @@ You can copy the `.env.example` file to `.env` and adjust it to your needs.
57
57
## Deployment with load-balancing
58
58
59
59
`docker-compose.yaml` allows to run a fishjam videoroom with multiple fishjams but all of that runs on the same machine.
60
-
For properly using load-balancing two machines will be needed and `docker-compose-deploy.yaml` will be used.
60
+
For properly using load-balancing two machines will be needed and `docker-compose-deploy.yaml` will be used.
61
61
You can see our deployment workflow [here](.github/workflows/test_build_and_deploy.yml).
62
-
This deployment is pretty simple.
62
+
This deployment is pretty simple.
63
63
All containers besides `fishjam2` are started on node1 and `fishjam2` is started on node2.
64
64
All environment variables used in our deployment are presented below:
65
65
66
66
```sh
67
67
DOMAIN=<FRONTEND_DOMAIN>
68
-
JF1_IP=<NODE1_IP># IP address of first node on which fishjam will be run
69
-
JF2_IP=<NODE2_IP># IP address of second node on which fishjam will be run
70
68
JF_SERVER_API_TOKEN=<API_TOKEN>#The same API token is used for all fishjams
71
-
JF1_HOST=<DOMAIN_FISHJAM1> OR <JF1_IP>:<FISHJAM1_PORT># Value passed to fishjam and returns by it when creating a room on this speicific fishjam
72
-
JF2_HOST=<DOMAIN_FISHJAM2> OR <JF2_IP>:<FISHJAM2_PORT>
73
-
BE_JF_ADDRESSES=<JF1_HOST><JF2_HOST>#Used by backend to create a notifier to one of fishjams
74
-
PROMETHEUS_TARGETS=<JF1_IP>:9568,<JF2_IP>:9568 #Addresses on which prometheus will query for data
69
+
BE_JF_ADDRESS=<DOMAIN_FISHJAM1> OR <FISHJAM_IP>:<FISHJAM_PORT>#Used by backend to create a notifier and to communicate with fishjam
70
+
PROMETHEUS_TARGETS=<FISHJAM_IP>:9568 #Addresses on which prometheus will query for data
0 commit comments