More verbose documentation...

[meirlazar]

Hey there, I am not new to the reverse proxy scene, using nginx proxy manager quite a bit prior to switching over but I was reading and rereading the documentation and what wasn't clear is when I need do I need to create a routing file versus using a docker-compose file, or do I need both, for example load balancing, does it need to be only with docker-swarm or can it be with standalone machines? Not to mention for those who might be savvy in linux and IT in general but don't know the ins and outs of http headers, rewrites, proxying, etc. there's definitely a steep learning curve. I mean I don't expect that everything will be exaplined to the most basic level, but perhaps a few more words/lines, examples thrown in will allow some of us to figure out the missing pieces. There's quite a bit of missing information that perhaps some may think is obvious but I definitely do not know. I can't tell you how many hours I spent on troubleshooting to try to figure out what I am doing. Thoughts?

[yusing]

do I need to create a routing file versus using a docker-compose file, or do I need both,

Route file: non docker services
Docker labels: docker / docker compose services

load balancing, does it need to be only with docker-swarm or can it be with standalone machines?

All routes with the same link property will be added to the load balancer, source does not matter (docker swarm or whatever)

there's definitely a steep learning curve

If you have some complext use case, sure. But for most self-hosters, starting a new service is just changing the container_name, running docker compose up -d then visit <container_name>.domain.tld.

[yusing]

I can't tell you how many hours I spent on troubleshooting to try to figure out what I am doing.

Could you explain more on what troubles you've been encountering with?