You're reading from Mastering Ubuntu Server Gain expertise in the art of deploying, configuring, managing, and troubleshooting Ubuntu Server

Product type Paperback

Published in Dec 2020

Publisher Packt

ISBN-13 9781800564640

Length 702 pages

Edition 3rd Edition

Tools

Ubuntu Server

Concepts

System Administration

Author (1):

Jay LaCroix

View More author details

Table of Contents (26) Chapters

Preface

1. Deploying Ubuntu Server

2. Managing Users and Permissions FREE CHAPTER

3. Managing Software Packages

4. Navigating and Essential Commands

5. Managing Files and Directories

6. Boosting Your Command-line Efficiency

7. Controlling and Managing Processes

8. Monitoring System Resources

9. Managing Storage Volumes

10. Connecting to Networks

11. Setting Up Network Services

12. Sharing and Transferring Files

13. Managing Databases

14. Serving Web Content

15. Automating Server Configuration with Ansible

16. Virtualization

17. Running Containers

18. Container Orchestration

19. Deploying Ubuntu in the Cloud

20. Automating Cloud Deployments with Terraform

21. Securing Your Server

22. Troubleshooting Ubuntu Servers

23. Preventing Disasters

24. Another Book You May Enjoy

25. Index

Installing and configuring NGINX

Apache isn't the only technology that is capable of allowing you to host web content on your server. NGINX also serves the same purpose and is gaining popularity quite rapidly. Although Apache is still the most common option right now, it's a good idea to at least be familiar with NGINX and learn its basics. NGINX itself is a proxy server as well, but is capable of also serving web content, which is why it competes with Apache. Serving web content is our focus for covering it in this section.

Before we do so, I want to mention first that you can really only have one web server service running on a single web server. If you've been following along up to now, you currently have a functional Apache web server. If you were to also install NGINX, it probably wouldn't start as the ports it wants to listen on (port 80 and/or 443) will already be in use. You can run both on a single server, but that's outside the scope of this...