Migrate deployment configuration to use NGINX

[azerella]

Enhancement

Our current deployment of this site is done with custom Node.js code, a static site such as ours should be an ideal candidate for something like NGINX. Because we are using custom Node.js server code, things like parsing uncommon MIME types such as .webmanifest, instead a 401 status is returned, in our staging configuration. This is no bueno.

@alex-page @sukhrajghuman
I would like to introduce the idea that we are currently handling the site deployment the wrong way. We're deploying a production grade site with simple express code, the site should be deployed as a static bundle with something like nginx or apache. The search functionality should be a seperate deployment that the static site fetches / posts to.

Issues:

• Site uses older HTTP 1/1 protocol. h2 is the new hotness.

• No gzip compression is in use, our assets could be way smaller.

• Separating the deployment and search functionality would reduce the page load time as we'd need to download less assets.

• I’ve read and understood the Contributing guidelines and have done my best effort to follow them.

• I’ve read and agree to the Code of Conduct.

• I’ve searched for any related issues and avoided creating a duplicate issue.

[alex-page]

I will need a bit of a better explanation, the lojk file should be getting read here?

[alex-page]

@adamzerella I am not too concerned about the staging or test instances, is this affecting live as well?