Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Nginx for Developers: An Introduction

carrot.is

Post reply on HN
Print view View original

11–20 of 142 posts

Re: Nginx for Developers: An Introduction

#11

Post by Adirael »

pajju wrote: post #8
samsnelling wrote: post #5

Completely off-topic: Is that a custom WP theme? I love the look and feel of this article. On-topic: Thank you for this. I am going to purchase a DO box this weekend and play around with nginx instead of apache. For some reason when I last tried to use nginx, I could not get location {} to work. Granted it was some time ago. Does anyone have any resources on nginx as a load balancer?

Avoid using Digital Ocean(DO). We had very very bad experience with them, file-system corruption, hardware failures. And we are still unable to recover all our data. And so far, no hope! They don't answer any of the questions properly, my team is very upset. We felt, they don't have much technical expertise in managing servers. DO might be okay for testing and learning, but never use them for any production setups. U…

My experience is the complete opposite. They've responded fast and helped when I needed them. They're cheap and fast enough.

I'm not too worried about data losses tho, we do regular offsite backups.

Re: Nginx for Developers: An Introduction

#12

Post by samsnelling »

jenius wrote: post #9
pajju wrote: post #8

Earlier quoted context omitted.

Avoid using Digital Ocean(DO). We had very very bad experience with them, file-system corruption, hardware failures. And we are still unable to recover all our data. And so far, no hope! They don't answer any of the questions properly, my team is very upset. We felt, they don't have much technical expertise in managing servers. DO might be okay for testing and learning, but never use them for any production setups. U…

On the contrary, if you just need a box to tinker with sysops stuff and learn, digital ocean is a fantastic solution. Cheap and I've never had a bad experience or anything unreliable. I can't speak to using it to store lots of not-backed-up files or running a gigantic production server, but for learning about syops it works great, to get back to the purpose of this article.

That's kind of where I'm at right now. Normally all of my side projects are hosted on PAAS (Appfog is my current choice, but we will see since their acquisition).

I really just want to practice setting up and tearing down configurations. I think DO will be a good choice for this.

Re: Nginx for Developers: An Introduction

#13

Post by samsnelling »

pajju wrote: post #8
samsnelling wrote: post #5

Completely off-topic: Is that a custom WP theme? I love the look and feel of this article. On-topic: Thank you for this. I am going to purchase a DO box this weekend and play around with nginx instead of apache. For some reason when I last tried to use nginx, I could not get location {} to work. Granted it was some time ago. Does anyone have any resources on nginx as a load balancer?

Avoid using Digital Ocean(DO). We had very very bad experience with them, file-system corruption, hardware failures. And we are still unable to recover all our data. And so far, no hope! They don't answer any of the questions properly, my team is very upset. We felt, they don't have much technical expertise in managing servers. DO might be okay for testing and learning, but never use them for any production setups. U…

Wow that sounds like it was quite an issue. Where are you thinking about migrating to? IMO, I can't really trust Linode anymore. MediaTemple is stupid expensive for VPS... Maybe SoftLayer? I've heard mixed reviews.

Re: Nginx for Developers: An Introduction

#16

Post by mrweasel »

warmwaffles wrote: post #15

I am a little hesitant on restarting nginx. When you do that, it drops the connections that are currently attached. Instead, you may want to do `nginx reload`

Yeah, I disliked that part to. The commands you need to know is:

nginx -t (test your configuration)

nginx -s reload (reload your configuration)

Also I prefer "nginx -s restart".

Re: Nginx for Developers: An Introduction

#17

Post by pajju »

samsnelling wrote: post #13
pajju wrote: post #8

Earlier quoted context omitted.

Avoid using Digital Ocean(DO). We had very very bad experience with them, file-system corruption, hardware failures. And we are still unable to recover all our data. And so far, no hope! They don't answer any of the questions properly, my team is very upset. We felt, they don't have much technical expertise in managing servers. DO might be okay for testing and learning, but never use them for any production setups. U…

Wow that sounds like it was quite an issue. Where are you thinking about migrating to? IMO, I can't really trust Linode anymore. MediaTemple is stupid expensive for VPS... Maybe SoftLayer? I've heard mixed reviews.

We are moving to SoftLayer or Hetzner.

They do more granular level monitoring to detect faulty hardware early and replace them faster.

Also greater technical support, having used both of them previously.

Re: Nginx for Developers: An Introduction

#18

Post by jenius »

mrweasel wrote: post #16
warmwaffles wrote: post #15

I am a little hesitant on restarting nginx. When you do that, it drops the connections that are currently attached. Instead, you may want to do `nginx reload`

Yeah, I disliked that part to. The commands you need to know is: nginx -t (test your configuration) nginx -s reload (reload your configuration) Also I prefer "nginx -s restart".

Great feedback guys - we'll look this over and probably change it in the article : )

The reason it's as such is because of what @timroman said in his reply, but if this method is no different and scales better no reason not to use it instead.

Re: Nginx for Developers: An Introduction

#20

Post by jenius »

samsnelling wrote: post #12
jenius wrote: post #9

Earlier quoted context omitted.

On the contrary, if you just need a box to tinker with sysops stuff and learn, digital ocean is a fantastic solution. Cheap and I've never had a bad experience or anything unreliable. I can't speak to using it to store lots of not-backed-up files or running a gigantic production server, but for learning about syops it works great, to get back to the purpose of this article.

That's kind of where I'm at right now. Normally all of my side projects are hosted on PAAS (Appfog is my current choice, but we will see since their acquisition). I really just want to practice setting up and tearing down configurations. I think DO will be a good choice for this.

Was in that exact same spot a couple months ago and did the same thing. I was eyeing DO for a while and one day folded and paid the (really no brainer) $5. I've learned a ton since then and it has been absolutely worth it for me.

I actually transitioned all my apps off any other PAAS platforms (mostly nodejitsu, timed nicely with their 3x price increase) and am now hosting everything I run off a single $5 digital ocean box, which actually is saving me a bit of money, and deploys are a lot smoother. The company I work at, Carrot, is also hosting all of carrot.is on a $5 DO box, including this article, which has had no issues coping with the 600+ people on site at a time that have come with this HN blitz.

Post reply on HN