self-hosted-docker-server-templates VS dip

So, in which order do I even go about this? I've installed Nginx-Proxy as a reverse proxy server but I can't get a working SSL with it. Tried installing some microservices but most of them need a functioning reverse proxy to get a working configuration. So it seems there's port forwarding in the router necessary, and my Asus RT-N66u has the settings for it but I never got it to work. So then I guess I'll need to self-host a router on the rPi and add a NAT-passthrough on the Asus. I see people posting their dashboards on here, sometimes with almost hundreds of microservices on them. How do you guys have time to set up all these, when it takes me days to not even get the reverse proxy working despite hours and hours of research, reading and troubleshooting? Like seriously, are there really no straightforward guides, or even better - compose files (kinda like this one, but just with a basic template) to get started with self hosting microservices (setup the network, add a dashboard)?

And then also add dip to get rid of these lengthy docker compose run prefixes from the every command typed in your console.

So, I went the old-fashioned way and added Dip to the mix. Now I can run all the familiar commands (bundle, rake, etc.) from my host system (with a dip prefix) without thinking about all the docker-compose --rm --it bla-bla. Moreover, I can cd into a subfolder (say, actioncable), and execute commands from there just like on a host machine:

And in this case this utility can safe us. DIP has two possible modes:

I'd be sure to also check out (if you haven't already) https://evilmartians.com/chronicles/ruby-on-whales-docker-for-ruby-rails-development, it might have some solutions to your problems, like using a cached Docker volume to mount your application's directory. Evil Martians also developed DIP to help make the Docker workflow more approachable.