Hosting a web application
Putting a site and an application into production: the domain name, the web server, the database, and deployments you can undo.
6 courses · about 570 minutes
This path assumes you can already keep a server running — it follows on from the administration path. It covers what happens once an application has to be reachable from outside: name resolution, Nginx in front of the application, the database, reversible deployments, and Docker where it actually earns its place.
What you will be able to do
- Publish a domain’s DNS records and verify them before waiting
- Serve a static site and put a Node application behind Nginx
- Deploy a new version without downtime, and roll it back
- Administer PostgreSQL: access, connections, and what makes it grow
- Decide when a container helps, and when it is a layer for nothing
The path
Understand how a name resolves, publish the right records, and diagnose with dig instead of waiting.
2 lessons · about 52 minutes
Serve a React/Vite build, put a Node.js or Next.js application behind a reverse proxy, and move to HTTPS.
4 lessons · about 88 minutes
Get the code onto the server, switch in a single operation, and be able to go back — including when the verification fails.
4 lessons · about 90 minutes
Who may connect, how many at once, what the database is doing right now, and why it takes more space than the data inside it.
4 lessons · about 92 minutes
What a container actually is, when to do without one, and how to put a Node application and its database behind a reverse proxy without exposing the machine.
5 lessons · about 108 minutes
Install the ISPConfig panel on Ubuntu Server, understand what it automates, and host a site and then a Node.js application on it.
5 lessons · about 140 minutes