In this course you will learn:
- How to deploy applications on a Linux server on an IaaS platform (Microsoft Azure).
- How to deploy applications on a PaaS platform (Render).
In pursuit of this goal, you will learn:
- How to use the command line and version control.
- The basics of Unix system administration and cloud computing architectures.
- Good security practices related to system administration and web applications.
This course is a Media Engineering web development course taught at HEIG-VD.
- Legend
- What you will need
- Plan
- How to improve our basic deployment
- More Practice
- Extra
- Frequently Asked Questions
- References
Parts of this guide are annotated with the following icons:
- 📖 Slides or written documents pertaining to the various topics discussed during this course.
- 🔨 An exercise aimed at practicing a topic discussed in class.
- 💥 This exercise is graded.
- 🔑 Solution(s) for an exercise.
- 🎥 A video related to a subject.
- 🏛️ The deployment architecture put in place during an exercise.
For you to succeed in this course, it is highly recommended that you read and complete all the content that is not labeled "extra".
- A Unix CLI
- Linux/macOS users can use their standard Terminal
- Windows users should install Git for Windows which includes Git Bash (or the WSL for more advanced users)
- Git
- macOS users should install the command-line tools
- Windows users should install Git for Windows
- Linux users on Debian/Ubuntu-based systems can install Git with the
sudo apt install gitcommand, or with their other distributions' package managers.
- A free GitHub account
- Google Chrome (recommended, any browser with developer tools will do)
- Firefox (optional, required for one network exercise)
- A free Render account
-
Introduction
-
Version control
-
Security
-
Basic deployment
-
Advanced deployment
- 🔨 Deploy a PHP application with Git
- 📖 Twelve-factor app
- 📖 Unix environment variables
- 🔨 Configure a PHP application through environment variables
- 📖 Linux process management
- 🔨 Manage a PHP application with systemd as a Process Manager
- 📖 Domain Name System (DNS)
- 🔨 Configure a domain name
- 📖 Reverse proxying
- 🔨 Deploy a static site with nginx
- 🔨 Deploy a PHP application with nginx and the FastCGI process manager
- 🔨 Deploy a multi-component web application with nginx
- 🔨 Horizontally scale a web application with nginx as a load balancer
- 📖 TLS/SSL certificates
- 🔨 Provision a Let's Encrypt TLS certificate with Certbot
-
Automated deployment
-
Graded deployment exercise
- 💥 🔨 Not yet available
-
Managed deployments
The basic SFTP deployment of the PHP TodoList has several flaws which we will fix during the rest of the course:
- Transfering files manually through SFTP is slow and error-prone. We will use Git to reliably transfer files from our central codebase and easily keep our deployment up-to-date over time.
- Hardcoding configuration is a bad practice. We will use environment variables so that our application can be dynamically configured and deployed in any environment without changing its source code.
- Starting our application manually is not suitable for a production deployment. We will use a process manager to manage the lifecycle of our application: starting it automatically when the server boots, and restarting it automatically if it crashes.
- Accessing a web application through an IP address is not user-friendly. We will obtain a domain and configure its DNS zone file so that our application is accessible with a human-readable domain name.
- Using a non-standard port is not user-friendly either. We will run the application on port 80 or 443 so that the end user does not have to specify a port in the browser's address bar.
- Running our application server directly on port 80 or 443 will cause a problem: only one process can listen on a given port at the same time. We need another tool to support multiple production deployments on the same server. That will be the job of a reverse proxy like Apache or nginx.
- Our application is not secure as indicated by the browser, because it is served over HTTP and not HTTPS. We will obtain a TLS/SSL certificate signed by a trusted certificate authority so that our application can be served over HTTPS and recognized as secure by browsers.
- The PHP Development Server is not meant to deploy applications in production environments. We will use the FastCGI Process Manager to perform a production-grade deployment, making our application more resilient and able to serve more clients concurrently.
Complete deployments
- 🔨 Deploy Flood It, a Spring Boot (Java) & Angular application with a PostgreSQL database
- 🔨 Deploy Minesweeper, a Phoenix (Elixir) & Alpine.js application with a PostgreSQL database
- 🔨 Deploy RPS, a Node.js & Svelte web application with a PostgreSQL database
- 🔨 🔨 Deploy WOPR, a Sinatra & Svelte application with a Redis database
- 🔨 Deploy One Chat Room, an Express (Node.js) web application with a MongoDB database
- 🔨 Deploy Big Browser, a Nest.js (Node.js) application with a Redis database
42
Read the command line cheatsheet
Read the system administration cheatsheet
Don't use something that is hard to remember. You're better off using a passphrase (here's a French version).
These are the main references used throughout this course. More detailed and additional links to various online articles and documentation can be found at the end of each subject.
- The Linux Documentation Project
- Building the Future of the Command Line
- SSH, The Secure Shell: The Definitive Guide - Daniel J. Barrett, Richard E. Silverman, Robert G. Byrnes
- The Git Book
- Open Web Application Security Project
- Ops School Curriculum
- The Internet Explained From First Principles
- The Twelve-Factor App
- Systemd Manual
- nginx documentation
- Render Documentation
Wikipedia is also often referenced, namely these and related articles: