Cloud server · Used for early projects
RainYun
A practical candidate for a website or small service. Choose by user region, configuration and measured workload rather than the lowest headline price.
LONG-RUNNING SERIES
Production Operations on a Single Server
A ten-part production path from architecture, systemd, Caddy and Docker Compose to secrets, backups, rollback, monitoring, troubleshooting and incident runbooks.
10/10published / target
- 01Servers & Deployment
Design a Single-Server Setup: Reverse Proxy, App, and Database
Draw the boundaries between the public entry point, reverse proxy, application, database, files, and backups so fewer ports are exposed and incidents are easier to diagnose.
- 02Servers & Deployment
Run a Web Application as a systemd Service
Move an app out of a temporary terminal session. Define a dedicated user, working directory, environment file, restart behavior, and logs, then verify the service safely.
- 03Servers & Deployment
Host Multiple Websites on One Server with Caddy
Route each domain to its own local service with Caddy. Check DNS, upstream addresses, HTTPS, configuration validation, safe reloads, and every affected site.
- 04Servers & Deployment
Docker Compose Production Readiness Checklist
Before moving a working Compose project into production, check image versions, builds, ports, internal networks, persistent volumes, health checks, restarts, and rollback.
- 05Servers & Deployment
Manage Production Secrets and Environment Files Safely
Separate ordinary configuration from secrets. Choose where to store .env files and service credentials, restrict access, avoid logging secrets, and plan rotation and incident response.
- 06Servers & Deployment
Back Up and Restore SQLite and PostgreSQL Databases
Choose a consistent backup method for SQLite or PostgreSQL, then document encryption, off-site storage, retention, verification, and a restore rehearsal in isolation.
- 07Servers & Deployment
Deploy on One Server with Health Checks and a Rollback Plan
Prepare and back up before release, start a candidate version, verify its health, switch traffic, observe the result, and keep a clear route back to the previous version.
- 08Servers & Deployment
What to Monitor on a Small Website Server
Start with user-visible availability, then watch application health, CPU, memory, disk, backup age, and logs. Set alerts that reflect sustained problems rather than brief spikes.
- 09Servers & Deployment
Troubleshoot 502, 504, and HTTPS Errors Layer by Layer
Trace faults through DNS, network access, TLS, Caddy, the local upstream, application, and database using evidence at each layer instead of blindly restarting the server.
- 10Servers & Deployment
Keep a Website Server Running with a Maintenance Checklist
Organize daily, weekly, monthly, and quarterly checks for availability, patches, capacity, backups, accounts, certificates, dependencies, and recovery drills.