On Fri, 20 Feb 2015 20:29:47 +0100, Sönke Ludwig wrote:
Yes that would be no problem.
I'm thinking of changing it so that if no bind address is specified in the configuration file then vibenews would just use the default HTTPServerSettings.bindAddresses list, which would expose it to the Internet. To make sure that existing users are not surprised by the new behavior, I will include a settings.json in the repo, which will change the bind address back to the current value of 127.0.0.1, and provide a convenient example of such configuration file. Does that sound OK?
This just has historical reasons (in the
sense that I'm personally just always had it running behind a proxy). Of
course a reverse proxy can also be useful to have for DoS protection
(where vibe.d doesn't have many countermeasures, yet), but everyone
should be able to decide how important that is.
OK, so the list so far of the advantages of using a reverse proxy is:
Better DoS control, due to vibe.d currently being weak in that area;
Is there anything else? I've quickly looked into the possibility of using nginx to allow no-downtime upgrades, but it wasn't clear to me how well the load balancing feature would work for that.