On Sat, 06 Feb 2016 20:36:23 GMT, Carl Sturtivant wrote:
Hello, I'm new to vibe.d, just read D Web Development, and I'm very very interested.
Do you recommend or is it typical to deploy behind an Nginx or other reverse proxy? This might be a good idea for non-vibe.d related reasons, under some circumstances, but I am asking if there are any additional vibe.d related reasons, given the current state of development. Of course this depends upon what is being deployed; I'd appreciate some discussion of this topic as an outsider.
I definitely recommend nginx if your site has over 2K daily visitors. After running without it for about 6 months, we were left with no other option but to install it. As our traffic increased, and we added translations, our site was crashing every hour or so due to the GC running. So I installed nginx first as a means of load-balancing, but then we transitioned everything related to the transport layer to it, since it also means less garbage generated by our app.
We deploy our sites in debug mode, so we can get nice callstacks, and nice error checking and whatnot. We let nginx deal with SSL, compression, static files, redirections, etc... Then all that's left is the actual site code handling the dynamic routes which is now considerably simplified. In addition to these, you also get HTTP2 working today by simply adding a directive in your config.
I am very happy with this setup, and recommend it.