61–70 of 142 posts
Good article. Be wary of the well documented zero-day exploits if you're using php. This is one of my other favorite articles: http://docs.ngx.cc/en/latest/topics/tutorials/config_pitfall... Some good introductory stuff here as well: http://pineapple.io/resources/tagged/nginx
http://tech.pro/tutorial/1335/devops-for-dummies-vps-configu...
It teaches you how to setup a DigitalOcean (or any other) VPS from scratch to host N amount of Rails applications using Nginx and Passenger. It took me some time to get things working properly and I distilled it into this short article that holds your hand and takes you from A to Z.
Good article. Be wary of the well documented zero-day exploits if you're using php. This is one of my other favorite articles: http://docs.ngx.cc/en/latest/topics/tutorials/config_pitfall... Some good introductory stuff here as well: http://pineapple.io/resources/tagged/nginx
How can a zero-day be well documented? By definition it's not yet public.
cgi.fix_pathinfo = 0If you like this article, I wrote a similar one called Devops for Dummies. http://tech.pro/tutorial/1335/devops-for-dummies-vps-configu... It teaches you how to setup a DigitalOcean (or any other) VPS from scratch to host N amount of Rails applications using Nginx and Passenger. It took me some time to get things working properly and I distilled it into this short article that holds your hand and takes you from A to…
I like just keeping a single "etc/nginx/sites" folder, including "sites/*.ON" in my main nginx.conf and then appending .ON to the sites that are enabled: active.site.com.ON another.active.com.ON not.active.com
It's kinda depressing that this article is basically just a copy of one I wrote in 2010 and it's still something that gets attention as interesting stuff. Nginx documentation obviously still has a long way to go.
I was more surprised than depressed about the upvotes for the current article. It really makes me wonder if the technical level of the audience here hasn't declined substantially. The current article is well written but it's aimed at a "Dummies" rather than developer level.
This article is just fine for IDE-side development, but I would not recommend for anyone to use the version of nginx in the standard Ubuntu package manager. It traditionally is several version back missing important key features that you might want to take advantage of.
Earlier quoted context omitted.
How can a zero-day be well documented? By definition it's not yet public.
It sounds scarier than saying: "If you use PHP, remember to set the following in your .ini" cgi.fix_pathinfo = 0
I like just keeping a single "etc/nginx/sites" folder, including "sites/*.ON" in my main nginx.conf and then appending .ON to the sites that are enabled: active.site.com.ON another.active.com.ON not.active.com
That's clever. Coming from Apache I was disappointed not to see something equivalent to: a2ensite (site)