thisNotMyName

thisNotMyName , 25 days ago

Whoah that is next level stupid.. it wouldn't need fact checkers if people weren't too dumb to evaluate sources

thisNotMyName , 30 days ago

*10.9 if not latest.
For the risk averse folks out there, check out https://github.com/containrrr/watchtower
I just let it run every night, so far w/o problems

thisNotMyName , 26 days ago

Sorry, I meant risk taking not averse (not my 1st language)
Regarding the bugs, they get usually fixed within days

thisNotMyName , 1 month ago

It's in the zoomed in circle in top left corner (it's the cringy 😂)

thisNotMyName , 2 months ago

I'd love that becoming a thing. TV OSs are always so shitty, I bet dedicated open source work would do wonders

thisNotMyName , 3 months ago

Zendaya switched to a dress after the red carpet walk, so you are probably right about the comfortability

thisNotMyName , 10 months ago

Welcome to the coldest summer for the rest of your life :)

thisNotMyName , 10 months ago

Since you already got a lot of ELI5s, here is a basic to-do to get you up and running. From my experience, since I use the exact same setup as you describe.

1. Set up your containers in a way you can reach them from you local network (e.g. http://123.456.789.10:123)
2. Get a domain name (you can get one at the registrar of your choice, e.g. mydomain.com)
3. Set up NGINX proxy manager (NPM) (default address of webui would be http://123.456.789.10:81)
4. Set up a new proxy host in NPM:
   • Domain name: mycontainer.mydomain.com
   • Scheme: http
   • Forward Hostname/IP: 123.456.789.10 (if you get an error later on, you can use the docker container name if NPM and your container are connected to the same Docker network)
   • Port: 123
   • Via access lists you can provide a very basic username/pw login to protect your sites (you can do more and cooler stuff with Authelia)
   • In the SSL tab you can (and should) setup the SSL encryption: https://www.youtube.com/watch?v=TBGOJA27m_0
5. Go to the DNS management of your registrar
   • Add an A-record for mydomain.com and the public IP of your server (you can google public IP to find it out)
   • Add a CNAME record for the subdomain with name mycontainer and target mydomain.com
6. open port 443 of your server in your router
   If everything worked right, you can visit mycontainer.mydomain.com, your DNS server will resolve this to your public IP and forwards the request to nginx, which will serve the data of your local container

thisNotMyName , 11 months ago

r/landchads would be really sad about this landphobia :/