Read a publisher called Wired
Look inside
No wires…
Read a publisher called Wired
Look inside
No wires…
Both nginx and apache are webservers and can do what you need.
Apache calls this Name-based Virtual Hosts. (see ServerName/ServerAlias)
Nginx calls this Name-based virtual servers (see server_name in the docs)
Either will listen on ports 80/443 on the IP and proxy the request depending on the hostname used. If you’re not really familiar with either, I would recommend nginx. It’s very popular, the documentation is good and the syntax is a lot better IMO.
I hear caddy is also a nice alternative with even simpler syntax, but I haven’t used it myself.
Good luck!
I can see how you’re not yet familiar with all these terms :p Both nginx and apache are http servers and work the exact same in your case.
The server (apache or nginx) listens on the IP on port 80 and 443. Depending on the hostname that is used to connect, the request is proxied to a different location. Apache calls this virtual hosts, nginx call this virtual servers
Please correct me if I’m wrong, but here’s what I think the situation is:
In that case you need both domains to connect to the same computer (because that’s the one with that IP address) which routes it to the correct location (either on the same computer or on a different one).
You basically have two solutions (that you already mentioned)
This is essentially the same, but instead of the services running locally, one or both run on different machines.
In both cases the IP address points to the machine running nginx.
If you can run both services on the same machine with docker, you should just use this: https://github.com/nginx-proxy/nginx-proxy
They finally banned AfD???
No, but still good news.