The deploying stub page will be rewritten sooon and the "What's next"
steps should migrate there. In the meantime this helps npm not break
when building the docs
The commit moves legacy.mdx to registration.mdx and significantly
shortens it. Instead of explaining every registration option now a table
is provided. Renaming the page because besides registration there is not
much else to explain about legacy auth. If anything, those should be
elaborated on the main authentication.mdx page (i.e. difference between
OAuth and UIAA)
The email section has also been updated with (some) relevant info.
Avoids some recursion and 404 endpoint issues. Serves as good
examples for future additions.
The "Intermittent federation failures to a specific server"
section is now ID'd as #intermittent for easier reachability.
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
stratself