forked from Fediversity/Fediversity
Expanded documentation for Element Call.
This commit is contained in:
parent
adbf25d990
commit
95e6b0e508
|
@ -123,8 +123,8 @@ chgrp -R www-data /etc/lk-jwt-service
|
||||||
chmod -R o-rwx /etc/lk-jwt-service
|
chmod -R o-rwx /etc/lk-jwt-service
|
||||||
```
|
```
|
||||||
|
|
||||||
The contents of `/etc/lk-jwt-service/config` are not fully known yet ([see
|
The contents of `/etc/lk-jwt-service/config` are not fully known yet (see
|
||||||
further, installation of the actual LiveKit, the SFU](#generatekeys)), but for now it's enough
|
further, installation of the actual LiveKit, the SFU), but for now it's enough
|
||||||
to fill it with this:
|
to fill it with this:
|
||||||
|
|
||||||
```
|
```
|
||||||
|
@ -158,7 +158,7 @@ You can do this as a normal user, it will use sudo to do its job.
|
||||||
Configuring this thing is [documented
|
Configuring this thing is [documented
|
||||||
here](https://docs.livekit.io/home/self-hosting/deployment/).
|
here](https://docs.livekit.io/home/self-hosting/deployment/).
|
||||||
|
|
||||||
Create a key and secret: {#generatekeys}
|
Create a key and secret:
|
||||||
|
|
||||||
```
|
```
|
||||||
livekit-server generate-keys
|
livekit-server generate-keys
|
||||||
|
@ -170,7 +170,7 @@ configuration file for livekit, `/etc/livekit/livekit.yaml`:
|
||||||
```
|
```
|
||||||
port: 7880
|
port: 7880
|
||||||
bind_addresses:
|
bind_addresses:
|
||||||
- ""
|
- ::1
|
||||||
rtc:
|
rtc:
|
||||||
tcp_port: 7881
|
tcp_port: 7881
|
||||||
port_range_start: 50000
|
port_range_start: 50000
|
||||||
|
@ -191,6 +191,11 @@ keys:
|
||||||
xxxxxxxxxxxxxxx: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
|
xxxxxxxxxxxxxxx: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
|
||||||
```
|
```
|
||||||
|
|
||||||
|
The LiveKit API listens on localhost, IPv6, port. This port is only used by
|
||||||
|
lk-jwt-service, so it shouldn't be reachable from the outside world.
|
||||||
|
|
||||||
|
The `xxx: xxxx` is the key and secret as generated before.
|
||||||
|
|
||||||
Now define a systemd servicefile, like this:
|
Now define a systemd servicefile, like this:
|
||||||
|
|
||||||
```
|
```
|
||||||
|
@ -261,3 +266,27 @@ cd element-call
|
||||||
After that, you can find the whole shebang under "dist". Copy that to
|
After that, you can find the whole shebang under "dist". Copy that to
|
||||||
`/var/www/element-call` and point nginx to it ([see nginx](../nginx#callwidget)).
|
`/var/www/element-call` and point nginx to it ([see nginx](../nginx#callwidget)).
|
||||||
|
|
||||||
|
It needs a tiny bit of configuring. The default configuration under `config/config.sample.json`
|
||||||
|
is a good place to start, copy it to `/etc/element-call` and change where
|
||||||
|
necessary:
|
||||||
|
|
||||||
|
```
|
||||||
|
{
|
||||||
|
"default_server_config": {
|
||||||
|
"m.homeserver": {
|
||||||
|
"base_url": "https://vm02199.matrixdev.example.com",
|
||||||
|
"server_name": "matrixdev.example.com"
|
||||||
|
}
|
||||||
|
},
|
||||||
|
|
||||||
|
"livekit": {
|
||||||
|
"livekit_service_url": "https://livekit.matrixdev.example.com"
|
||||||
|
},
|
||||||
|
|
||||||
|
"features": {
|
||||||
|
"feature_use_device_session_member_events": true
|
||||||
|
},
|
||||||
|
|
||||||
|
"eula": "https://www.example.com/online-EULA.pdf"
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
Loading…
Reference in a new issue