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
How to draw a single server production structure: reverse agents, applications, databases and port boundaries
A landingable deployment map will be used to demarcate the boundaries of the public network portal, reverse agents, application processes, databases, files and backups, reducing blind screening of port exposures and malfunctions.
- 02Servers & Deployment
Use systemd Host site applications: users, environmental files, restarts and logs
Collapse the process of running the website by hand as systemd Service to identify dedicated users, work directories, environmental files, start-up commands, automatic restarts and log views, and to maintain a secure authentication order.
- 03Servers & Deployment
A server hosts multiple websites:Caddy Reverse Agent & Configure Authentication
Use Caddy Transmit multiple websites by domain name to different local ports, process them DNS Upstream address, configuration split,HTTPS, authenticate and uninterruptible load to avoid changing a station to affect all domain names.
- 04Servers & Deployment
Docker Compose Pre-natal examination: mirrors, networks, rolls and health checks
It'll be activated on the computer. Compose The project is organized as a maintenanceable production deployment, examining mirror versions, construction, ports, internal networks, permanent rolls, health checks, restarts and updates on a case-by-case basis.
- 05Servers & Deployment
How do you put the key to the production environment:.env Documentation authority, rotation and disclosure processing
Distinguishing normal configurations from sensitive keys, combing .env, systemd EnvironmentFile Packagings secrets Use boundaries and establish privileges, backups, rotations and processing sequences for suspected leaks.
- 06Servers & Deployment
Backup is not a copy file:SQLite, PostgreSQL Rehearsals
We're going to have to split. SQLite and PostgreSQL Select a consistent back-up method to record encryption, off-site preservation, retention cycles and verifications, and use the isolation environment to resume exercises to demonstrate that backup is actually available.
- 07Servers & Deployment
How to reduce interruptions in single server releases: health check, switch and quick rollback
Dismantling releases into preparation, backup, start-up candidate versions, health certification, traffic switch and observation, retaining the previous version and rollback conditions, and avoiding a failure to reconfigure them at the production site.
- 08Servers & Deployment
Server surveillance first looks at what:CPU, memory, disk, log and alarm thresholds
Create small server monitoring from user usability: check domain names and HTTPS, applied health,CPU, memory, disk, backup age and log anomalies, and use duration to reduce misreporting.
- 09Servers & Deployment
502, 504 and HTTPS How to check the fault: from DNS Error stratification to application
Press DNS Networks,TLS, Caddy and the order of local upstream, application and database HTTPS Error, narrowing the range with each layer of evidence to avoid any luck in restarting the server.
- 10Servers & Deployment
Website operations are stable by checklist: patches, capacity, failure logs and recovery manual
Server maintenance is divided into daily, weekly, monthly and quarterly tasks, covering patches, capacity, backups, accounts, certificates, dependency and recovery exercises, and establishing operational manuals that are directly visible during periods of failure.