Following some discussions in the support room, this env is best made
redundant. It is only recommended as a workaround for some scenarios
where Caddy fails to detect the ingress network.
However, Docker breaks this by appending prefixes to network names.
The other approach of:
```diff
services:
caddy:
+ environment:
+ - CADDY_INGRESS_NETWORKS=proxy
networks:
proxy:
+ name: proxy
```
Can be suggested, but probably not necessary to document.
See https://github.com/lucaslorentz/caddy-docker-proxy/issues/207
for further details
As lk-jwt-service is hosted in a bridge network, the previous
`extra_hosts` using 127.0.0.1 would just loop back to the container
itself. Using `network_mode: host` is unnecessary, and the
`host-gateway` approach works well for both Podman and Docker
Host loopback issues are prevalent in non-Livekit scenarios too: push
gateways is another example. Considering moving these to a dedicated
Docker section of the troubleshooting page.
These are mostly grammar fixes. Furthermore:
* docs(docker,delegation): Use `important` admonitions in some places
* docs(maintenance): Elaborate on `immutable` directive in media header
* Use 2-spaces indentation instead of 4
* Use `proxy` as network name instead of `caddy` to be consistent
* Mount Caddyfile for delegated example as well
The `configs.content` approach only works for Docker, so doing this
would be more inclusive for Podman users
Also removed Nexy's forge as it is currently limited access
I am a very responsible and organised maintainer and this was a deliberate plan to see how many users are keeping an active watch on the project's releases /j
* Make all links indirect for better maintenance
* Add Domain section with `coturn.example.com` and use it in subsequent
examples
* Add standard ports for TURN and TURNS
* Remove TURNS-over-UDP (unknown whether it is supported)
* Add section on opening ports with ufw commands
* IMPORTANT: Move password auth/guest access instructions into the
Appendix as they are very insecure
* Small improvements in Testing section
* Rewrite Troubleshooting section to be more concise and cut down on
errors
* Add note to Eturnal in Appendix section
koshchki123