Self hosting involves 3 steps in my life.
1) Find the docker compose file. 2) Change the expose line to make it specific 10.0.10.1:9000 instead of the default 0.0.0.0:9000 . 3) Connect via wireguard.
(Answers the "security" point a sister comment brought up too)
Not to mention the 100 steps you have to do to get their, of course...
Yes of course. The first time you try to get wireguard working you will not get it to ping the other side right away. It is a process. The next few times it'll be much quicker. Then it will keep running forever. Or maybe mine isn't working but I never noticed.
I had this wireguard setup in place long before I even ran my first docker container. It's all building on top of things already there.
It's really frustrating how every single compose file publishes on 0.0.0.0 instead of 127.0.0.1
and goodbye security...
Yes. It's implicit. Goodbye security indeed.