dandri/continuwuity
1
0
Fork 0
mirror of https://forgejo.ellis.link/continuwuation/continuwuity/ synced 2026-08-22 15:39:48 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs: Replace docker-compose with docker compose

Browse Source
This commit is contained in:
stratself
2026-08-05 18:00:11 +00:00
committed by Ellis Git
parent 2144317933
commit c7160edc13
2 changed files with 7 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/calls/livekit.mdx
+3 -3
View File
@@ -282,7 +282,7 @@ ### 6. Start Everything
## Testing
To test that LiveKit is successfully integrated with Continuwuity, you will need to replicate its [Token Exchange Flow](https://github.com/element-hq/lk-jwt-service#%EF%B8%8F-how-it-works--token-exchange-flow). Follow the steps below while checking Docker logs (`docker-compose logs --follow`), in order to help [troubleshooting](#troubleshooting) any issues.
To test that LiveKit is successfully integrated with Continuwuity, you will need to replicate its [Token Exchange Flow](https://github.com/element-hq/lk-jwt-service#%EF%B8%8F-how-it-works--token-exchange-flow). Follow the steps below while checking Docker logs (`docker compose logs --follow`), in order to help [troubleshooting](#troubleshooting) any issues.
First, you will need an access token for your current login session. These can be found in your client's settings or obtained via [this website](https://timedout.uk/mxtoken.html).
@@ -353,7 +353,7 @@ ## Testing
## Troubleshooting
To debug any issues, you can place a call or redo the Testing instructions, and check the container logs for any specific errors. Use `docker-compose logs --follow` to follow these logs in real-time.
To debug any issues, you can place a call or redo the Testing instructions, and check the container logs for any specific errors. Use `docker compose logs --follow` to follow these logs in real-time.
### Common errors in Element Call UI
@@ -507,7 +507,7 @@ ### if you're using `network_mode: host`, you can skip this part
# "3478:3478/udp" # (optional UDP port)
```
Recreate the LiveKit container (with `docker-compose up -d livekit`) to apply these changes. Remember to allow the new `50300:50400/udp` ports through your firewall.
Recreate the LiveKit container (with `docker compose up -d livekit`) to apply these changes. Remember to allow the new `50300:50400/udp` ports through your firewall.
Then, we will configure a route from port 443 of the host back to our `livekit-turn.example.com` service on port 5349. To both **multiplex** this and LiveKit's websocket on the same port, we will use a layer-4 reverse proxy with **SNI routing** capabilities, such as [caddy-l4][caddy-l4] on the host system.
docs/deploying/docker.mdx
+4 -6
View File
@@ -174,7 +174,7 @@ ### Starting Your Server
4. Check your server logs for a registration token:
```bash
docker-compose logs continuwuity 2>&1
docker compose logs continuwuity 2>&1
```
You'll see output as below.
@@ -203,13 +203,11 @@ ## Updating
```bash
# stop the services in docker-compose.yaml
docker-compose down
docker compose down
# pull latest images for the services in docker-compose.yaml
docker-compose pull
docker compose pull
# spin up the containers again
docker-compose up -d
docker compose up -d
```
## Other deployment methods