" nginx (pronounced engine-x). " I have literally never heard anyone call it that.
Nginx for Developers: An Introduction
81–90 of 142 posts
Re: Nginx for Developers: An Introduction
#82" nginx (pronounced engine-x). " I have literally never heard anyone call it that.
Well, me, I had never talked or heard anyone talk in "real"-life about nginx before up until one month ago and apparently, it's pronounced that way.
Look here: http://wiki.nginx.org/Pronunciation
Re: Nginx for Developers: An Introduction
#83[deleted]
Re: Nginx for Developers: An Introduction
#84If 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…
Thank you for linking to your article, it was perfect timing as I'm about to throw up a tiny Ruby/Sinatra/PostgreSQL site I've been making for a local need. The quality of my actual code aside, I understand that servers are incredibly complex beasts, especially when it comes to security, and I want to ask (And because of their complexity, I assume it's a small question with a huge, complex answer), how relatively 'safe' would I be following a guide like yours along with other ones that specify some simple, good practices for setting up a server?
By safe, I mean in the context of the server getting hacked. I know people wouldn't bother but I'd rather at least feel a tiny bit safe. I'm going with a VPS (Digital Ocean) too so I can slowly learn all these things.
Re: Nginx for Developers: An Introduction
#85" nginx (pronounced engine-x). " I have literally never heard anyone call it that.
I have literally never heard it called anything else, even before it started getting traction. I'm curious how you've heard it said before?
Re: Nginx for Developers: An Introduction
#86If 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…
One thing I would recommend is searching for deals on LowEndBox[1] blog. Most of the popular VPS's are ridiculously overpriced compared to what you can find on LowEndBox. It's a good site to get advice and reviews of various VPS providers, too.
Re: Nginx for Developers: An Introduction
#87Slightly off-topic, but I'm sad that people still use apt-get. aptitude is pretty much just better[1].
Also, if you're reading this article you probably don't need the slightly better performance/throughput of nginx. Nginx's configuration is just terrible. You can cause segfaults and all sorts of unexpected behavior with the If directive[2]. And who came up with the idea that rewrite[3] should sometimes redirect instead of rewriting?
If the replacement string begins with http:// then the client will be redirected, and any further rewrite directives are terminated.
Apache's configuration might be ugly and unwieldy and the community might be horribly infested, but at least the configuration makes sense. Lighttpd has none of the above problems, though.
[1] http://superuser.com/questions/93437/
Re: Nginx for Developers: An Introduction
#88Slightly off-topic, but I'm sad that people still use apt-get. aptitude is pretty much just better[1]. Also, if you're reading this article you probably don't need the slightly better performance/throughput of nginx. Nginx's configuration is just terrible. You can cause segfaults and all sorts of unexpected behavior with the If directive[2]. And who came up with the idea that rewrite[3] should sometimes redirect inst…
Well Ubuntu doesn't ship aptitude by default any more which would explain parts of it.
Re: Nginx for Developers: An Introduction
#89If 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…
Thank you for linking to your article, it was perfect timing as I'm about to throw up a tiny Ruby/Sinatra/PostgreSQL site I've been making for a local need. The quality of my actual code aside, I understand that servers are incredibly complex beasts, especially when it comes to security, and I want to ask (And because of their complexity, I assume it's a small question with a huge, complex answer), how relatively 'sa…
Hi thanks for your comments, I appreciate you taking the time to read it.
I'm _not_ a devops guy. Following my guide you _will_ get a running production server but I've only distilled things from other blogs I've hunted on the web. I would make sure I hire someone who actually does this for a living before putting production things on something I configured.
So feel safe, but cautiously safe - I'm not a guru.
Re: Nginx for Developers: An Introduction
#90What makes this "for developers"? Whats the difference if a sysadmin is reading this, or a Linux user? Im surprised to see this on the frontpage, it is less than basics in anything any hacker worth its name can do.
I think it should read "Web Developers" - those who may be less experienced in setting up a web server like nginx.
Why would a Web Developer be less experienced in setting up a Web server than a Developer?
- a touchy Web Developer :)