What problem does it solve?
Turn a cloud Linux server into a securely reachable web host by providing a structured, vendor-agnostic workflow that covers SSH hardening, firewall posture, Nginx configuration for static sites or app backends, DNS routing, TLS with ACME, and safe HTTP-to-HTTPS redirects, plus optional post-launch tuning such as BBR.
Core Features & Use Cases
- Intake and routing: identify distro family, access model, DNS status, hosting goal.
- Prerequisites and secure access: confirm server access, domain ownership, and key-based SSH login; verify docs against official sources.
- Firewall and exposure: enforce a deny-by-default policy and expose only ports 80 and 443 when the web path is ready; keep app backends private on loopback.
- Web server setup: install and validate Nginx, choose between static-site hosting or app proxy, and ensure proper config layout.
- TLS/HTTPS: obtain and renew certificates via Let’s Encrypt or ACME clients; validate DNS and HTTP challenges before redirecting traffic.
- Validation and optional tuning: verify HTTPS works before enabling redirects and defer BBR/network tuning until the secure path is stable.
Quick Start
Begin by identifying the distro family and verifying official docs for current package names, service units, and ACME guidance before attempting any commands.
