Member-only story
ABSTRACT
I think you’ve just gotten yourself new self-managed server. Congratulations on a wise decision! In this article we’re going to look at disabling Apache, then installing & activating NGINX on a new server. It assumes a certain level of previous server administration knowledge, or at least a willingness to learn.
NOTE: This article is not meant to serve as a guide for migrating existing sites on a production server from Apache to NGINX. Please keep that in mind when following the steps below, as one of the steps we’ll take is turning Apache off. Doing so on a server with live production sites will bring sites down until they are reconfigured for NGINX.
INTRODUCTION
NGINX (pronounced “Engine Ex”) was released for production in 2004 and is rapidly becoming a popular alternative to the traditional Apache web server. It features an event-driven design, which can make better use of today’s computer hardware than Apache’s process-driven design. Because of this, NGINX is often seen as the “faster” alternative to Apache, being able to handle a higher load of concurrent connections while using less resources. There are many comparisons out there between Apache and NGINX; we’ll leave the debate up to the community. But here are a few pointers that outline the key reasons to choose Apache…
