• 53 Posts
  • 1.23K Comments
Joined 2 years ago
cake
Cake day: July 2nd, 2023

help-circle






  • Sure, sure, old man. Everything was better when you were young.

    There never was a majority of people who were into computers. It was always a minority. And I’d argue that nowadays there’s more developers because there’s simply more people with access to computers.

    Some of them won’t like them, some will be neutral and some will be “geeking around”.

    And having seen some code from people both older and younger, the younger ones are better (note that it’s my anecdotal evidence). And you at least can train the younger ones, while the “experienced” will argue with you and take energy out of your day.

    I’m so tired of the stupid “when I was young, everything was better”. You know what else was exactly the same? The previous generation telling you how everything was better when they were young. Congrats, you’re them now.












  • As others have said, you have bound your host port 8080 to container port 9090 and then you use caddy to reverse proxy to container port 8080, which doesn’t exist.

    As for DNS, it’s just a translation system - you send a domain, it returns its IP (for A or AAAA), everything else is done on server. So your current setup works.

    Yes, you can deactivate the port, if you’re not gonna use it on the host, you don’t need it. Since you’re connecting via the internal network, you’re not using the bound ports.

    As a side note, use some firewall and disable everything but 80, 443 and 22, you should not leave other ports open, especially if you’re binding all the ports in docker like that.

    And perhaps make it a good habit to bind ports to 127.0.0.1 by default, that way no one outside the local server can access them. You can do it like this: “127.0.0.1:8080:9090”