23.3. Linux Server Setup
Table of Contents
Why Linux For Backend Servers
Most production backends run on Linux. It is free, stable, scriptable, and most server tools are built for it first.
As a backend developer you do not need to become a full Linux administrator, but you must be comfortable enough to:
- Log in to a remote server
- Move around the filesystem
- Install packages and services
- Configure your app to run as a service
- Secure basic access
This chapter focuses on what you actually do when you get a fresh Linux server for deployment.
Goal of this chapter
After this chapter you should be able to log into a new Linux VPS, perform basic setup, and prepare it to run a backend application.
Choosing a Linux Distribution
For servers you almost always use a distribution like:
| Family | Examples | Package manager | Typical usage |
|---|---|---|---|
| Debian-based | Ubuntu Server, Debian | apt | Very common for web apps and VPS |
| RHEL-based | CentOS Stream, Rocky, Alma | dnf / yum | Enterprise data centers |
| Others | Arch, openSUSE | Various | Less common for beginners on servers |
For this course, you can assume Ubuntu Server LTS on a cloud VPS, because:
- Many tutorials use it
- Most hosting providers offer it
- The
aptpackage manager is beginner friendly
If you see examples using dnf or yum, you can usually translate them:
| Action | Ubuntu / Debian | RHEL family |
|---|---|---|
| Update packages | sudo apt update | sudo dnf update |
| Upgrade system | sudo apt upgrade | sudo dnf upgrade |
| Install package | sudo apt install nginx | sudo dnf install nginx |
| Remove package | sudo apt remove nginx | sudo dnf remove nginx |
Connecting To Your Server With SSH
You normally access a remote Linux server using SSH (Secure Shell).
Creating an SSH key
On your local machine (Linux, macOS, or WSL on Windows):
ssh-keygen -t ed25519 -C "your_email@example.com"You will be asked:
- Where to save: press Enter to accept default
~/.ssh/id_ed25519 - Passphrase: choose a strong passphrase, or leave empty for no passphrase
This creates two files:
| File | Description |
|---|---|
~/.ssh/id_ed25519 | Private key, keep it secret |
~/.ssh/id_ed25519.pub | Public key, safe to share |
Important
Never share your private key (id_ed25519 or id_rsa). Share only the .pub file.
View your public key:
cat ~/.ssh/id_ed25519.pubCopy this line. You will add it to the server.
Adding your SSH key to the server
Most cloud providers (DigitalOcean, AWS, etc.) let you paste your SSH public key during server creation. They put it into /home/youruser/.ssh/authorized_keys for you.
If you only have password access initially, you can:
- Connect with password:
ssh root@YOUR_SERVER_IP- On the server, create the
.sshdirectory for your user:
mkdir -p ~/.ssh
chmod 700 ~/.ssh- Edit
authorized_keysand paste your public key:
nano ~/.ssh/authorized_keys
# paste the content of your .pub key
chmod 600 ~/.ssh/authorized_keysAfter that, you can log in with your key.
Logging in via SSH
From your local machine:
ssh youruser@YOUR_SERVER_IP
If you are using the default root user (not recommended long term):
ssh root@YOUR_SERVER_IPYou will see a shell prompt like:
youruser@server-name:~$You are now working on the remote server.
Creating a Non-Root User
Running everything as root is dangerous. A safer pattern:
- Create a regular user.
- Give it
sudopermissions.
As root on the server:
adduser deploy
# follow prompts for password and info
Add the user to the sudo group (on Ubuntu):
usermod -aG sudo deploySwitch to that user:
su - deploy
Now test sudo:
sudo ls /root
It should ask for deploy's password and then show the directory listing.
Next, copy your SSH authorized keys from root to deploy (if the provider added them to root):
rsync --archive --chown=deploy:deploy /root/.ssh /home/deploy
Now you can exit and reconnect as deploy:
exit # leave root
ssh deploy@YOUR_SERVER_IP
From now on, use this non-root user with sudo for administration.
Basic File System Navigation
When you log in you are in your home directory, for example /home/deploy.
Useful paths on a server:
| Path | Purpose |
|---|---|
/home/user | User home directories |
/var/www | Often used for web app code |
/etc | Configuration files for services |
/var/log | Log files |
/usr/bin | System binaries |
/tmp | Temporary files |
Basic commands:
pwd # show current directory
ls # list files
ls -la # list with details and hidden files
cd /var/www # change directory
cd ~ # go back to home
mkdir myapp # create directory
rm file.txt # remove file
rm -r dir # remove directory recursivelyExample session:
cd /var
ls
cd www
sudo mkdir myapp
sudo chown deploy:deploy myapp
cd myapp
pwd # /var/www/myappInstalling System Packages
On Ubuntu and similar:
- Update package index:
sudo apt update- Upgrade installed packages:
sudo apt upgrade- Install a package, for example Git:
sudo apt install git- Remove a package:
sudo apt remove git- Search for packages:
apt search postgresSome typical packages for backend servers:
| Purpose | Package examples |
|---|---|
| Web server | nginx |
| Database client | postgresql-client, mysql-client |
| VCS | git |
| Basic tools | curl, wget, htop, zip |
| Python | python3, python3-venv, python3-pip |
System Users, Groups, and Permissions
Linux has users and groups. Each file has an owner, a group, and three sets of permissions:
- Owner permissions
- Group permissions
- Other (everyone else) permissions
See file details:
ls -lYou might see:
-rw-r--r-- 1 deploy deploy 1234 Aug 28 12:00 config.json
drwxr-xr-x 2 deploy deploy 4096 Aug 28 12:01 logsBreakdown of the first line:
| Part | Meaning |
|---|---|
-rw-r--r-- | File type and permissions |
deploy | Owner |
deploy | Group |
Permissions are in order r (read), w (write), x (execute):
rw-for owner: read + writer--for group: read onlyr--for others: read only
Change owner:
sudo chown deploy:deploy /var/www/myappChange permissions:
chmod 640 config.json # owner rw, group r, others none
chmod 755 scripts.sh # typical for executable scriptsTypical app dir permissions
- Application code:
deploy:deploy,755directories,644files - Configuration files with secrets:
600or640, owner-only or owner+group
Process Management and Services
You will need to:
- Check if your app or dependency services are running
- Start, stop, and restart services
Checking processes
Use ps or htop:
ps aux | grep python
This lists running processes. htop (if installed) is interactive:
sudo apt install htop
htopsystemd services
Most modern distributions use systemd with systemctl to manage services.
Common commands:
# Check service status
sudo systemctl status nginx
# Start / stop / restart
sudo systemctl start nginx
sudo systemctl stop nginx
sudo systemctl restart nginx
# Enable service on boot
sudo systemctl enable nginx
# Disable on boot
sudo systemctl disable nginxShortcut to see if a service is running:
systemctl is-active nginx
# prints: active, inactive, failed, etc.Opening, Editing, and Viewing Files
You must be able to edit configuration files on the server.
Useful tools:
| Tool | Type | Usage |
|---|---|---|
cat | Viewer | Print a file |
less | Pager | Scroll through a file |
nano | Text editor, easy | Good for beginners |
vim | Advanced editor | Powerful but steeper learning curve |
Examples:
cat /etc/os-release # view OS info
less /var/log/syslog # scroll system log
nano /etc/nginx/nginx.conf # edit nginx config
In nano:
- Edit text
Ctrl+Oto saveCtrl+Xto exit
Basic Networking on the Server
You often need to:
- Check the server IP
- Test connectivity
- See which ports your app listens on
Checking the IP address
ip a
Look for something like inet 203.0.113.10/24 on a non-loopback interface, that is your server IP.
Testing connectivity
To check if you can reach a host:
ping google.com
# Ctrl+C to stopTo fetch a URL from the server:
curl https://example.comChecking listening ports
To see which ports your server is listening on, use ss:
sudo ss -tulnpOptions:
-tTCP-uUDP-llistening sockets-nnumeric output-pshow process
Typical output line:
LISTEN 0 128 0.0.0.0:80 0.0.0.0:* users:(("nginx",pid=1234,fd=6))
This means nginx is listening on port 80 on all network interfaces.
Firewalls and Basic Security
On Ubuntu, a simple firewall tool is UFW (Uncomplicated Firewall).
Basic UFW usage
Install (if not present):
sudo apt install ufwCheck status:
sudo ufw statusAllow SSH and HTTP/HTTPS:
sudo ufw allow OpenSSH
sudo ufw allow http
sudo ufw allow httpsEnable firewall:
sudo ufw enableList rules:
sudo ufw status numberedDelete a rule:
sudo ufw delete 1 # deletes rule number 1 from the list
Careful with firewalls
Always ensure SSH is allowed before enabling the firewall, or you can lock yourself out:
sudo ufw allow OpenSSH first, then sudo ufw enable.
Installing Runtime Environments
You will install your app runtime, for example Python or Node.js. The exact details belong to other chapters, but the general server-side pattern is similar.
Example: Python runtime on Ubuntu
Install Python and tools:
sudo apt update
sudo apt install python3 python3-venv python3-pipVerify:
python3 --version
pip3 --versionCreate a directory for your app:
sudo mkdir -p /var/www/myapp
sudo chown deploy:deploy /var/www/myapp
cd /var/www/myappCreate a virtual environment:
python3 -m venv venv
source venv/bin/activate
pip install fastapi uvicorn[standard]You now have a Python environment dedicated to this app.
Running Your Application as a Service
Running your app in a terminal with uvicorn main:app is not enough for production. You want:
- The app to start on boot
- Automatic restart if it crashes
- Logs captured in the system
On systemd systems you create a service unit.
Example systemd service for a FastAPI app
Assume:
- Code lives in
/var/www/myapp - Virtual environment in
/var/www/myapp/venv - Uvicorn command:
uvicorn main:app --host 0.0.0.0 --port 8000
Create a service file:
sudo nano /etc/systemd/system/myapp.serviceContents:
[Unit]
Description=My FastAPI Application
After=network.target
[Service]
User=deploy
Group=deploy
WorkingDirectory=/var/www/myapp
Environment="PATH=/var/www/myapp/venv/bin"
ExecStart=/var/www/myapp/venv/bin/uvicorn main:app --host 0.0.0.0 --port 8000
Restart=always
RestartSec=3
[Install]
WantedBy=multi-user.targetSave and exit.
Reload systemd:
sudo systemctl daemon-reloadStart and enable:
sudo systemctl start myapp
sudo systemctl enable myappCheck status:
sudo systemctl status myappYou can now stop / start / restart your app via:
sudo systemctl restart myappLogs:
journalctl -u myapp -f
-f follows logs in real time, like tail -f.
Logs and Monitoring Basics
Logs help you debug issues on a live server.
Common log locations:
| Type | Location examples |
|---|---|
| System logs | /var/log/syslog, /var/log/messages |
| Auth logs | /var/log/auth.log |
| Nginx logs | /var/log/nginx/access.log, error.log |
| App logs | Custom, often under /var/www/myapp/logs |
View logs:
sudo tail -n 100 /var/log/syslog
sudo tail -f /var/log/nginx/error.log
For systemd services:
journalctl -u myapp -n 50 # last 50 lines
journalctl -u myapp -f # followLearning to read logs is critical for troubleshooting in production.
Simple Troubleshooting Workflow
When your backend is "not working" on a Linux server, use a systematic approach.
Example checklist:
- Is the app service running?
sudo systemctl status myapp- Any recent errors in app logs?
journalctl -u myapp -n 50- Is the app listening on the expected port?
sudo ss -tulnp | grep 8000- Can the server itself reach the app?
curl http://127.0.0.1:8000/health- Is the firewall letting traffic through?
sudo ufw status- If behind Nginx or another reverse proxy, are its logs clean?
sudo tail -n 100 /var/log/nginx/error.logAs you gain experience, this kind of routine becomes quicker and mostly automatic.
Summary
In this chapter you learned:
- Why backend servers commonly use Linux
- How to connect to a server via SSH using key-based authentication
- How to create a non-root user with
sudo - Basic filesystem navigation and permissions
- Installing packages with
apt - Managing services with
systemctl - Editing configuration files on the server
- Inspecting network ports and setting up a simple firewall with UFW
- Installing a runtime environment and running your app as a
systemdservice - Where to find and read logs, and a basic troubleshooting workflow
These are the core Linux skills you need to prepare a server for production deployment. In the next chapters you will build on this foundation to containerize and deploy your backend applications.
Views: 0
Where to Move
Move chapter:
- ☰ 1. Introduction to Backend Development
- ☰ 1.1. What Is Backend Development?
- ☰ 1.2. Frontend vs Backend
- ☰ 1.3. How Web Applications Work
- ☰ 1.4. Client-Server Architecture
- ☰ 1.5. Request-Response Cycle
- ☰ 1.6. Static vs Dynamic Websites
- ☰ 1.7. Backend Developer Responsibilities
- ☰ 1.8. Backend Development Roadmap
-
- ☰ 2. How the Web Works
- ☰ 2.1. The Internet and the Web
- ☰ 2.2. IP Addresses
- ☰ 2.3. Domain Names
- ☰ 2.4. DNS
- ☰ 2.5. Ports
- ☰ 2.6. TCP/IP Basics
- ☰ 2.7. HTTP and HTTPS
- ☰ 2.8. HTTP Requests
- ☰ 2.9. HTTP Responses
- ☰ 2.10. HTTP Methods
- ☰ 2.11. HTTP Status Codes
- ☰ 2.12. HTTP Headers
- ☰ 2.13. Cookies
- ☰ 2.14. Sessions
- ☰ 2.15. What Happens When You Enter a URL?
-
- ☰ 3. Development Environment
- ☰ 3.1. Choosing an Operating System
- ☰ 3.2. Linux Basics for Backend Developers
- ☰ 3.3. Command Line Basics
- ☰ 3.4. Environment Variables
- ☰ 3.5. Installing Development Tools
- ☰ 3.6. Code Editors and IDEs
- ☰ 3.7. Git
- ☰ 3.8. GitHub and GitLab
- ☰ 3.9. Creating Your First Repository
- ☰ 3.10. Branches and Commits
- ☰ 3.11. Basic Git Workflow
-
- ☰ 4. Programming Fundamentals
- ☰ 4.1. Variables and Data Types
- ☰ 4.2. Operators
- ☰ 4.3. Conditions
- ☰ 4.4. Loops
- ☰ 4.5. Functions
- ☰ 4.6. Data Structures
- ☰ 4.7. Error Handling
- ☰ 4.8. Modules and Packages
- ☰ 4.9. File Handling
- ☰ 4.10. Object-Oriented Programming
- ☰ 4.11. Classes and Objects
- ☰ 4.12. Inheritance and Composition
- ☰ 4.13. Clean Code Principles
-
- ☰ 5. Python for Backend Development
- ☰ 5.1. Introduction to Python
- ☰ 5.2. Installing Python
- ☰ 5.3. Virtual Environments
- ☰ 5.4. pip and Package Management
- ☰ 5.5. Python Project Structure
- ☰ 5.6. Functions and Type Hints
- ☰ 5.7. Classes and Dataclasses
- ☰ 5.8. Exceptions
- ☰ 5.9. Working with Files
- ☰ 5.9.1. File Downloads
- ☰ 5.9.2. File Validation
- ☰ 5.9.3. Image Uploads
- ☰ 5.9.4. Local File Storage
- ☰ 5.9.5. Object Storage
- ☰ 5.9.6. S3-Compatible Storage
- ☰ 5.9.7. Presigned URLs
- ☰ 5.9.8. Secure File Handling
-
- ☰ 5.10. JSON
- ☰ 5.11. Date and Time
- ☰ 5.12. Logging
- ☰ 5.13. Configuration
- ☰ 5.14. Environment Variables
- ☰ 5.15. Async Programming
- ☰ 5.16. Python Backend Best Practices
-
- ☰ 6. Introduction to Web Backends
- ☰ 6.1. Building a Simple Web Server
- ☰ 6.2. Routing
- ☰ 6.3. URL Parameters
- ☰ 6.4. Query Parameters
- ☰ 6.5. Request Bodies
- ☰ 6.6. Form Data
- ☰ 6.7. JSON Requests
- ☰ 6.8. Returning Responses
- ☰ 6.9. Templates
- ☰ 6.10. Static Files
- ☰ 6.11. Middleware
- ☰ 6.12. Application Configuration
-
- ☰ 7. REST APIs
- ☰ 7.1. What Is an API?
- ☰ 7.2. What Is REST?
- ☰ 7.3. Resources and Endpoints
- ☰ 7.4. RESTful URL Design
- ☰ 7.5. HTTP Methods in REST
- ☰ 7.6. GET Requests
- ☰ 7.7. POST Requests
- ☰ 7.8. PUT Requests
- ☰ 7.9. PATCH Requests
- ☰ 7.10. DELETE Requests
- ☰ 7.11. Request Validation
- ☰ 7.12. Response Models
- ☰ 7.13. HTTP Status Codes
- ☰ 7.14. Error Responses
- ☰ 7.15. Pagination
- ☰ 7.16. Filtering
- ☰ 7.17. Sorting
- ☰ 7.18. Searching
- ☰ 7.19. API Versioning
- ☰ 7.20. API Documentation
- ☰ 7.21. OpenAPI and Swagger
-
- ☰ 8. FastAPI
- ☰ 8.1. Introduction to FastAPI
- ☰ 8.2. Routes and Path Operations
- ☰ 8.3. Path Parameters
- ☰ 8.4. Pydantic Models
- ☰ 8.5. Data Validation
- ☰ 8.6. Dependency Injection
- ☰ 8.7. Exception Handling
- ☰ 8.8. Background Tasks
- ☰ 8.9. File Uploads
- ☰ 8.10. Async Endpoints
- ☰ 8.11. FastAPI Project Structure
- ☰ 8.12. Building a Complete REST API
-
- ☰ 9. Databases
- ☰ 9.1. Introduction to Databases
- ☰ 9.2. Relational vs NoSQL Databases
- ☰ 9.3. Tables, Rows, and Columns
- ☰ 9.4. Primary Keys
- ☰ 9.5. Foreign Keys
- ☰ 9.6. Relationships
- ☰ 9.7. One-to-One Relationships
- ☰ 9.8. One-to-Many Relationships
- ☰ 9.9. Many-to-Many Relationships
- ☰ 9.10. Database Schema Design
- ☰ 9.11. Normalization
- ☰ 9.12. Indexes
- ☰ 9.13. Transactions
- ☰ 9.14. ACID Properties
-
- ☰ 10. SQL
- ☰ 10.1. Introduction to SQL
- ☰ 10.2. CREATE
- ☰ 10.3. INSERT
- ☰ 10.4. SELECT
- ☰ 10.5. UPDATE
- ☰ 10.6. DELETE
- ☰ 10.7. WHERE
- ☰ 10.8. ORDER BY
- ☰ 10.9. GROUP BY
- ☰ 10.10. Aggregate Functions
- ☰ 10.11. JOINs
- ☰ 10.12. Subqueries
- ☰ 10.13. Constraints
- ☰ 10.14. Indexes
- ☰ 10.15. Transactions
- ☰ 10.16. Common Table Expressions
- ☰ 10.17. SQL Performance Basics
-
- ☰ 11. PostgreSQL
- ☰ 11.1. Introduction to PostgreSQL
- ☰ 11.2. Installing PostgreSQL
- ☰ 11.3. Creating Databases
- ☰ 11.4. Users and Roles
- ☰ 11.5. Permissions
- ☰ 11.6. PostgreSQL Data Types
- ☰ 11.7. Constraints
- ☰ 11.8. Indexes
- ☰ 11.9. Transactions
- ☰ 11.10. JSON Data
- ☰ 11.11. Backup and Restore
- ☰ 11.12. PostgreSQL Performance Basics
-
- ☰ 12. ORM and Database Integration
- ☰ 12.1. What Is an ORM?
- ☰ 12.2. SQLAlchemy
- ☰ 12.3. Models
- ☰ 12.4. Database Sessions
- ☰ 12.5. Creating Records
- ☰ 12.6. Reading Records
- ☰ 12.7. Updating Records
- ☰ 12.8. Deleting Records
- ☰ 12.9. Relationships
- ☰ 12.10. Queries
- ☰ 12.11. Transactions
- ☰ 12.12. Connection Pooling
- ☰ 12.13. Database Migrations
- ☰ 12.14. Alembic
- ☰ 12.15. Repository Pattern
-
- ☰ 13. Authentication
- ☰ 13.1. Authentication vs Authorization
- ☰ 13.2. Password Storage
- ☰ 13.3. Password Hashing
- ☰ 13.4. Registration
- ☰ 13.5. Login
- ☰ 13.6. Tokens
- ☰ 13.7. JSON Web Tokens
- ☰ 13.8. Access Tokens
- ☰ 13.9. Refresh Tokens
- ☰ 13.10. OAuth 2.0
- ☰ 13.11. OpenID Connect
- ☰ 13.12. Social Login
- ☰ 13.13. Logout
- ☰ 13.14. Password Reset
- ☰ 13.15. Email Verification
- ☰ 13.16. Multi-Factor Authentication
-
- ☰ 14. Authorization
- ☰ 14.1. Users and Permissions
- ☰ 14.2. Role-Based Access Control
- ☰ 14.3. Permission-Based Access Control
- ☰ 14.4. Protecting API Endpoints
- ☰ 14.5. Admin Permissions
- ☰ 14.6. Resource Ownership
- ☰ 14.7. Authorization Best Practices
-
- ☰ 15. Backend Security
- ☰ 15.1. Introduction to Web Security
- ☰ 15.2. HTTPS and TLS
- ☰ 15.3. SQL Injection
- ☰ 15.4. Cross-Site Scripting
- ☰ 15.5. Cross-Site Request Forgery
- ☰ 15.6. CORS
- ☰ 15.7. Authentication Attacks
- ☰ 15.8. Brute-Force Protection
- ☰ 15.9. Rate Limiting
- ☰ 15.10. Input Validation
- ☰ 15.11. Secure Password Storage
- ☰ 15.12. Secrets Management
- ☰ 15.13. Secure Cookies
- ☰ 15.14. Security Headers
- ☰ 15.15. File Upload Security
- ☰ 15.16. Dependency Vulnerabilities
- ☰ 15.17. OWASP Top 10
-
- ☰ 16. Caching
- ☰ 16.1. Why Caching Matters
- ☰ 16.2. Application Caching
- ☰ 16.3. Redis
- ☰ 16.3.1. Introduction to Redis
- ☰ 16.3.2. Installing Redis
- ☰ 16.3.3. Keys and Values
- ☰ 16.3.4. Expiration
- ☰ 16.3.5. Distributed Locks
-
- ☰ 16.4. Cache Keys
- ☰ 16.5. Cache Invalidation
- ☰ 16.6. Caching Database Queries
- ☰ 16.7. Distributed Caching
-
- ☰ 17. Background Processing
- ☰ 17.1. Synchronous vs Asynchronous Tasks
- ☰ 17.2. Background Jobs
- ☰ 17.3. Message Queues
- ☰ 17.4. Celery
- ☰ 17.5. Redis as a Message Broker
- ☰ 17.6. Scheduled Tasks
- ☰ 17.7. Retry Strategies
- ☰ 17.8. Handling Failed Jobs
- ☰ 17.9. Email Jobs
- ☰ 17.10. Long-Running Tasks
-
- ☰ 18. Email
- ☰ 18.1. How Email Works
- ☰ 18.2. SMTP
- ☰ 18.3. Sending Emails
- ☰ 18.4. HTML Emails
- ☰ 18.5. Transactional Emails
- ☰ 18.6. Password Reset Emails
- ☰ 18.7. Background Email Delivery
- ☰ 18.8. Email Delivery Best Practices
-
- ☰ 19. Testing
- ☰ 19.1. Why Backend Testing Matters
- ☰ 19.2. Unit Testing
- ☰ 19.3. Integration Testing
- ☰ 19.4. API Testing
- ☰ 19.5. pytest
- ☰ 19.6. Fixtures
- ☰ 19.7. Mocking
- ☰ 19.8. Testing Databases
- ☰ 19.9. Testing Authentication
- ☰ 19.10. Testing FastAPI
- ☰ 19.11. Test Coverage
- ☰ 19.12. Automated Testing
-
- ☰ 20. Logging and Monitoring
- ☰ 20.1. Application Logging
- ☰ 20.2. Log Levels
- ☰ 20.3. Structured Logging
- ☰ 20.4. Request Logging
- ☰ 20.5. Error Logging
- ☰ 20.6. Metrics
- ☰ 20.7. Health Checks
- ☰ 20.8. Monitoring
- ☰ 20.9. Prometheus
- ☰ 20.10. Grafana
- ☰ 20.11. Alerting
- ☰ 20.12. Error Tracking
- ☰ 20.13. Observability Basics
-
- ☰ 21. Docker
- ☰ 21.1. Introduction to Containers
- ☰ 21.2. Docker Architecture
- ☰ 21.3. Images
- ☰ 21.4. Containers
- ☰ 21.5. Dockerfiles
- ☰ 21.6. Building Images
- ☰ 21.7. Running Containers
- ☰ 21.8. Volumes
- ☰ 21.9. Networks
- ☰ 21.10. Docker Compose
- ☰ 21.11. FastAPI with Docker
- ☰ 21.12. PostgreSQL with Docker
- ☰ 21.13. Redis with Docker
- ☰ 21.14. Multi-Container Applications
- ☰ 21.15. Production Docker Best Practices
-
- ☰ 22. Web Servers and Reverse Proxies
- ☰ 22.1. Application Servers
- ☰ 22.2. Uvicorn
- ☰ 22.3. Gunicorn
- ☰ 22.4. Reverse Proxies
- ☰ 22.5. Nginx
- ☰ 22.6. Traefik
- ☰ 22.7. HTTPS
- ☰ 22.8. TLS Certificates
- ☰ 22.9. Let's Encrypt
- ☰ 22.10. Load Balancing
-
- ☰ 23. Deployment
- ☰ 23.1. Development vs Production
- ☰ 23.2. Preparing an Application for Production
- ☰ 23.3. Linux Server Setup
- ☰ 23.4. Deploying with Docker
- ☰ 23.5. Environment Configuration
- ☰ 23.6. Managing Secrets
- ☰ 23.7. HTTPS Configuration
- ☰ 23.8. Production Logging
- ☰ 23.9. Backups
- ☰ 23.10. Zero-Downtime Deployment
- ☰ 23.11. Rollbacks
-
- ☰ 24. CI/CD
- ☰ 24.1. Introduction to CI/CD
- ☰ 24.2. Continuous Integration
- ☰ 24.3. Continuous Delivery
- ☰ 24.4. Continuous Deployment
- ☰ 24.5. CI/CD Pipelines
- ☰ 24.6. GitHub Actions
- ☰ 24.7. GitLab CI/CD
- ☰ 24.8. Building Docker Images
- ☰ 24.9. Container Registries
- ☰ 24.10. Deployment Pipelines
- ☰ 24.11. Staging Environments
- ☰ 24.12. Production Environments
- ☰ 24.13. Rollback Strategies
-
- ☰ 25. Backend Architecture
- ☰ 25.1. Monolithic Architecture
- ☰ 25.2. Modular Monoliths
- ☰ 25.3. Microservices
- ☰ 25.4. Layered Architecture
- ☰ 25.5. Service Layer
- ☰ 25.6. Separation of Concerns
- ☰ 25.7. Domain-Driven Design Basics
- ☰ 25.8. Event-Driven Architecture
- ☰ 25.9. Choosing an Architecture
-
- ☰ 26. Performance and Scalability
- ☰ 26.1. Understanding Backend Performance
- ☰ 26.2. CPU-Bound vs I/O-Bound Work
- ☰ 26.3. Asynchronous Programming
- ☰ 26.4. Database Optimization
- ☰ 26.5. Query Optimization
- ☰ 26.6. Indexing
- ☰ 26.7. Load Balancing
- ☰ 26.8. Horizontal Scaling
- ☰ 26.9. Vertical Scaling
- ☰ 26.10. Stateless Applications
- ☰ 26.11. Performance Testing
- ☰ 26.12. Load Testing
-
- ☰ 27. Advanced API Development
- ☰ 27.1. WebSockets
- ☰ 27.2. Server-Sent Events
- ☰ 27.3. GraphQL
- ☰ 27.4. Webhooks
- ☰ 27.5. Idempotency
- ☰ 27.6. API Rate Limiting
- ☰ 27.7. API Keys
- ☰ 27.8. API Gateways
- ☰ 27.9. Distributed APIs
- ☰ 27.10. Real-Time Applications
-
- ☰ 28. Production Backend Engineering
- ☰ 28.1. Configuration Management
- ☰ 28.2. Database Backups
- ☰ 28.3. Disaster Recovery
- ☰ 28.4. Graceful Shutdown
- ☰ 28.5. Fault Tolerance
- ☰ 28.6. Circuit Breakers
- ☰ 28.7. High Availability
- ☰ 28.8. Monitoring Production Systems
- ☰ 28.9. Incident Response
-
- ☰ 29. Project 1: Task Management API
- ☰ 29.1. Project Requirements
- ☰ 29.2. Project Structure
- ☰ 29.3. Database Design
- ☰ 29.4. CRUD Operations
- ☰ 29.5. Validation
-
- ☰ 30. Project 2: Authentication System
- ☰ 30.1. User Registration
- ☰ 30.2. JWT Authentication
- ☰ 30.3. Role-Based Authorization
- ☰ 30.4. Security Testing
-
- ☰ 31. Project 3: E-Commerce Backend
- ☰ 31.1. Architecture
- ☰ 31.2. User Management
- ☰ 31.3. Product Management
- ☰ 31.4. Categories
- ☰ 31.5. Shopping Cart
- ☰ 31.6. Orders
- ☰ 31.7. Inventory
- ☰ 31.8. Payments
- ☰ 31.9. Admin API
-
- ☰ 32. Final Project: Production Backend
- ☰ 32.1. Planning the Application
- ☰ 32.2. Designing the Architecture
- ☰ 32.3. Designing the Database
- ☰ 32.4. Building the REST API
- ☰ 32.5. Authentication and Authorization
- ☰ 32.6. PostgreSQL Integration
- ☰ 32.7. Redis Integration
- ☰ 32.8. Background Workers
- ☰ 32.9. File Storage
- ☰ 32.10. Dockerizing the Application
- ☰ 32.11. CI/CD Pipeline
- ☰ 32.12. Production Deployment
- ☰ 32.13. HTTPS and Domain Setup
- ☰ 32.14. Performance Optimization
- ☰ 32.15. Security Review
- ☰ 32.16. Documentation
-
- ☰ 33. Backend Developer Roadmap
- ☰ 33.1. What You Should Know Now
- ☰ 33.2. Building a Portfolio
- ☰ 33.3. Creating Backend Projects
- ☰ 33.4. Contributing to Open Source
- ☰ 33.5. Preparing for Backend Interviews
- ☰ 33.6. Backend Interview Questions
- ☰ 33.7. Database Interview Questions
- ☰ 33.8. API Interview Questions
- ☰ 33.9. Linux and Docker Interview Questions
- ☰ 33.10. Where to Go Next
-
Comments
Please login to add a comment.
Don't have an account? Register now!