In this first episode of Linux Server Admin with Fexingo, Lucas and Luna dive into a real-world incident at a mid-sized e-commerce company where a single typo in a deployment script — a missing dash in a rm command — took down the entire production fleet for 47 minutes. They walk through the timeline: what happened, how the team detected it via a sudden spike in 5xx errors, the immediate rollback with a Git revert, and the post-mortem that led to mandatory peer review for any script containing rm, chmod, or sudo. Along the way, they establish the show's rhythm: specific numbers, real commands, practical lessons — no fluff. Lucas explains the concept of a blast radius and why the team should have used a canary deployment. Luna pushes back on the peer-review policy, arguing it could slow down urgent fixes. By the end, they preview future episodes covering topics like systemd unit hardening, journalctl log analysis, and SSH key management. No introductions, no outro — just two sysadmins talking shop.

#LinuxServerAdmin #Sysadmin #Bash #ServerEngineering #Technology #ProductionIncident #RmCommand #DeploymentScript #GitRevert #BlastRadius #CanaryDeployment #PeerReview #PostMortem #FiveHundredErrors #LinuxCommandLine #ServerFailure #SiteReliabilityEngineering #FexingoBusiness

Keep every episode free: buymeacoffee.com/fexingo