![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/da10e5c4-016d-4b47-954e-d42f320bc52d.png)
I think you can achieve it with a reverse-proxy. Let’s say that domain.com points at server 0, you’ll have to put a reverse proxy that answers all calls. In the config of the reverse proxy you’ll have to redirect the services based on the domain. I’m using Caddy and this example should work:
0.domain.com {
reverse_proxy http://X.X.X.X:8080
}
1.domain.com {
reverse_proxy http://Y.Y.Y.Y:8123
}
And so on.
EDIT: Looks like I was late to the party! +1 to @greco reply as it’s more complete and clear (especially on the risks of this approach)
That’s because linuxserver focuses on creating docker images for existing projects.
Usually if you check a product on linuxserver.io is because you know already the product and you want to find a good quality docker (docker compose) image.
All the github and docker pages from linuxserver have the same structure and after the generic intro they present the project.
Personally I love what they’re doing but I understand your confusion, it was the same for me when I first knew of the project.