Everybody loves their random port numbers these days, but I still prefer custom hostnames.
Just chuck an entry into your hosts file and tell your web server to sniff for it and you’re done. Run your stuff on port 80 like nature intended and never have to teach either end of your app how to deal with colons and numbers in domain names.
And you get to skip the six paragraphs of pain the other commenters are describing, orchestrating their kubernetes and whatnot.
I like to combine both locally — bind to port 0 to get an arbitrary unprivileged port, and use domains in /etc/hosts for easier configuration ;-)
For those not familiar with what you are talking about, you can add things like the following to your /etc/hosts file:
127.0.1.1 foo.local
127.0.2.4 foo.bar.local
...
They will all resolve to local host, so make sure to bind your services to those IP addresses (eg. `nc -l 127.0.2.4 80` will bind only to 127.0.2.4 on port 80).
But running on unprivileged ports like 80 means you've got to run the server as root.
How does that work with binding the same port to it? Does it automatically assign a new IP to every new domain resolv() call gets (and then caches it)?
Just chuck an entry into your hosts file and tell your web server to sniff for it and you’re done. Run your stuff on port 80 like nature intended and never have to teach either end of your app how to deal with colons and numbers in domain names.
And you get to skip the six paragraphs of pain the other commenters are describing, orchestrating their kubernetes and whatnot.
e.g.: http://dev.whatever/