Do you really need to put vibenews behind a reverse proxy? What are the benefits? Is it only that is is better (e.g., better performance) or is it really recommended (e.g., vibe.d craps out with some problematic HTTP requests)?
For now I'm using only listenHTTPReverseProxy() from another vibe.d process, so if the recommendation is due to limitations of vibe.d then I guess that doesn't help a single bit. To put vibenews directly listening on the public IP address I would have to change (fork) the code, since it seems that bit isn't configurable, which is a bit of maintenance hassle. Would you accept a pull request that allowed setting the hostName from the default "127.0.0.1" to something else?