Stupid question. How do you share IPs if all the websites on a machine are running their own webserver? When running in IIS, IIS handles the virtual hosts. Unless we found a massive stach of IPv4 IPs?
So you set up the self hosted webservers on some non routable local IPs / ports, and set up IIS to map these IPs / ports to the external IP / hostname?
Sounds complicated. You have two states to maintain and keep synced. The .net core servers and IIS.
It's done with Node.js and nginx all the time. Other than the initial configuration nginx is essentially stateless, and there's simple setups out there to automate the nginx config as well, with docker for example: https://github.com/jwilder/nginx-proxy.
Comments
Stupid question. How do you share IPs if all the websites on a machine are running their own webserver? When running in IIS, IIS handles the virtual hosts. Unless we found a massive stach of IPv4 IPs?
nginx reverse proxy would be relatively simple.
There's even some docs straight from the asp.net site[0].
It's a bit of a paradigm shift from the "old" way but it's quite a normal thing to do with Node.js for example.
[0] - https://docs.asp.net/en/latest/publishing/linuxproduction.ht...
You typically still use IIS but only as a reverse proxy
So you set up the self hosted webservers on some non routable local IPs / ports, and set up IIS to map these IPs / ports to the external IP / hostname?
Sounds complicated. You have two states to maintain and keep synced. The .net core servers and IIS.
It's done with Node.js and nginx all the time. Other than the initial configuration nginx is essentially stateless, and there's simple setups out there to automate the nginx config as well, with docker for example: https://github.com/jwilder/nginx-proxy.
Of course it's complicated, you stipulated that all websites are running their own web server.
I am not. This seems to be what .net core does, according to the article.