NGINX MAINLAND?

NGINX MAINLAND?

by: Music47ell
2 minutes to read

Recently I took a DigitalOcean{.thirstylink} server for a spin to try both PHP 7 and nginx with HTTP/2.

I tried installing nginx from the package that comes with Ubuntu but it turns out that it installed an older version of nginx that doesn’t support HTTP/2.

The default package with Ubuntu 14.04 trusty have nginx version 1.4.6-1. But HTTP/2 support comes with nginx 1.9.5.

No problem. Google comes to the rescue.

A bit of research and I found out which version of nginx support HTTP/2.

I didn’t know that nginx have a public “beta” package for people to test the latest features.

Most services call that package beta, dev or pre release.

Some companies go for unique names like bleeding edge in the case of WordPress or canary like Chrome.

With nginx it’s different, it’s called mainline. My eyes apparently weren’t function that well when I looked at it.

So what I seen was this:

NGINX MAINLAND

Yes. That’s right. I read it: NGINX MAINLAND.

And honestly I kinda like the name mainland more, it’s like the place where the raw, source code is available.

You would think it would be riddled with bugs, but according to this post from the nginx blog, it’s not:

Note that stable does not mean more reliable or more bug-free. In fact, the mainline is generally regarded as more reliable because we port all bug fixes to it, and not just critical fixes as for the stable branch.

Oh, you thought we were done? Nope. I wish.

So when I first read about nginx mainline, I contacted DigitalOcean and asked if what I was doing is correct. Lo and behold, I kept telling the customer support person, nginx mainland, instead of mainline.

When I realized what I did, I face-palmed myself so hard 😛

All in all, it was a funny thing to misread but apparently I need to focus more from now on while I’m reading. Ha!