Packt+ | Advance your knowledge in tech

You're reading from Building Enterprise JavaScript Applications Learn to build and deploy robust JavaScript applications using Cucumber, Mocha, Jenkins, Docker, and Kubernetes

Product type Paperback

Published in Sep 2018

Publisher Packt

ISBN-13 9781788477321

Length 764 pages

Edition 1st Edition

Languages

JavaScript

Tools

Cucumber

Concepts

Application Development

Author (1):

Daniel Li

View More author details

Table of Contents (20) Chapters

Preface

1. The Importance of Good Code FREE CHAPTER

2. The State of JavaScript

3. Managing Version History with Git

4. Setting Up Development Tools

5. Writing End-to-End Tests

6. Storing Data in Elasticsearch

7. Modularizing Our Code

8. Writing Unit/Integration Tests

9. Designing Our API

10. Deploying Our Application on a VPS

11. Continuous Integration

12. Security – Authentication and Authorization

13. Documenting Our API

14. Creating UI with React

15. E2E Testing in React

16. Managing States with Redux

17. Migrating to Docker

18. Robust Infrastructure with Kubernetes

19. Other Books You May Enjoy

Leave a review - let other readers know what you think

Setting up NGINX

So let's get NGINX installed on our machine!

Note

We will outline the installation instructions for NGINX on Ubuntu. Installation for other platforms can be found at nginx.com/resources/wiki/start/topics/tutorials/install/.

By default, the nginx package should already be in Ubuntu's default repositories:

hobnob@hobnob:$ apt-cache show nginx
Package: nginx
Architecture: all
Version: 1.14.0-0ubuntu1
...

However, we should use the official NGINX repository to ensure we always get the most up-to-date version. To do this, we need to add NGINX's package repository to the list of repositories that Ubuntu will search for when it tries to download packages.

By default, there are two places that Ubuntu will search: inside the /etc/apt/sources.list file and inside files under the /etc/apt/sources.list.d/ directory. We should not write directly to the /etc/apt/sources.list file because when we upgrade our distribution, this file will be overwritten. Instead, we should create a new file...