Hacker News Reader

So they deployed a bad config file to all nodes and restarted the service, which then failed to start.

How is this specific to Nginx? This same mistake is possible with any other software ever written.

nginx is faster at stop/starting?

downvoters: I'm deadly serious. I've seen plenty of deployment systems which were unbearably slow because it gave more time for a human to spot a bad deploy and cancel it, and who were afraid to replace it with something faster because it would lack this safety net.

Any pointers for those interested in the story who have no clue?

Great story bro

What does "en-masse configuration" even mean?

That they deployed a broken config file & forcefully stop-started nginx instead of reloading it (and bypassing nginx's built-in protection: it will test a config and refuse to load it if it's broken on reload. on restart it's stuck with whatever busted config you give it).