Linux Server Admin with Fexingo: Sysadmin, Bash, and Server Engineering

Linux Server Admin with Fexingo: Sysadmin, Bash, and Server Engineering

By FexingoBusiness
Download on the App Store

Linux Server Admin with Fexingo: Sysadmin, Bash, and Server Engineering episodes

  • How Container Orchestration Went Mainstream

    In this episode of Linux Server Admin with Fexingo, hosts Lucas and Luna explore the real-world impact of container orchestration on Linux server engineering. They trace the journey from early Docker days to Kubernetes becoming the default deployment platform for everything from microservices to batch jobs. Lucas breaks down why container orchestration isn't just for tech giants: small teams can spin up a three-node cluster with k3s in under an hour, cutting deployment time from 45 minutes to 90 seconds. The hosts discuss the hidden costs: network complexity, storage challenges, and the learning curve for sysadmins who grew up with bare metal. They cite a 2025 Cloud Native Computing Foundation survey showing 72 percent of organizations now run container orchestration in production, up from 39 percent in 2020. Luna pushes back on the 'just use Docker' argument, and Lucas explains why operators — the human or automated kind — are the unsung heroes of containerized infrastructure. Perfect for sysadmins wondering whether to jump into Kubernetes or wait for the next abstraction.

    #ContainerOrchestration #Kubernetes #Docker #LinuxServerAdmin #Sysadmin #Bash #ServerEngineering #k3s #CNCF #ProductionDeployments #Microservices #DevOps #Technology #CloudNative #Ops #FexingoBusiness #BusinessPodcast #Infrastructure

    Keep every episode free: buymeacoffee.com/fexingo

    10 min
  • Why You Should Monitor Server Disk Latency Now

    Episode 8 of Linux Server Admin with Fexingo. Lucas and Luna drill into disk I/O latency — the silent performance killer that most sysadmins ignore until it's too late. They walk through a real 2025 case: how a mid-sized e-commerce platform lost 12 percent of checkout conversions because their monitoring dashboard showed CPU and RAM as green while storage latency was spiking. You'll learn what 'iowait' actually means, why average latency numbers lie, and how a single 'iotop' command can save your weekend. No hype, just practical server engineering.

    #DiskLatency #IOWait #LinuxPerformance #ServerMonitoring #StoragePerformance #iotop #iostat #FexingoBusiness #BusinessPodcast #Sysadmin #ServerEngineering #Bash #DevOps #Infrastructure #TechOps #LinuxAdmin #PerformanceTuning #Ecommerce

    Keep every episode free: buymeacoffee.com/fexingo

    11 min
  • Automating Server Backups With Borgmatic

    In this episode, Lucas and Luna dive into the practical world of server backups using Borgmatic, a wrapper for the Borg backup tool. They walk through a real disaster scenario where a rogue script deleted a week's worth of customer transactions on a staging server, and how a Borgmatic backup saved the day. The discussion covers the key advantages of deduplication, encryption, and incremental backups, along with a concrete setup example using a crontab. Lucas explains how Borg's chunking algorithm reduces storage by 80 percent compared to traditional tar files, and why append-only mode protects against ransomware. The hosts also touch on common pitfalls like forgetting to test restores and the importance of off-site storage. By the end, listeners will have a clear, actionable template for automating their own nightly backups with Borgmatic, including a sample configuration file for a small web application database.

    #Borgmatic #BorgBackup #ServerBackup #LinuxBackup #DisasterRecovery #Deduplication #Encryption #IncrementalBackup #Crontab #RansomwareProtection #AppendOnly #Sysadmin #BashScripting #ServerEngineering #Technology #LinuxServer #BackupStrategy #FexingoBusiness

    Keep every episode free: buymeacoffee.com/fexingo

    12 min
  • The Case for Structured Server Documentation

    Lucas and Luna make the case that structured server documentation—not just comments in config files, but a living runbook—is the single most impactful investment a sysadmin can make. They walk through a concrete example: a senior engineer at a mid-size SaaS company who spent two weeks building a Markdown-based runbook repository, and how it saved the team 40 hours during a critical PagerDuty escalation six months later. They discuss documentation formats, automation hooks, and the social challenge of getting a team to actually maintain the thing. No flame wars over wiki versus docs-as-code—just practical advice for teams that are tired of 'who knows what that cron job does'.

    #ServerDocumentation #Sysadmin #Runbooks #DevOps #Linux #Bash #ServerEngineering #IncidentResponse #DocumentationAsCode #TeamWorkflow #PagerDuty #Markdown #SaaSOps #ConfigurationManagement #ITOps #FexingoBusiness #BusinessPodcast #Technology

    Keep every episode free: buymeacoffee.com/fexingo

    13 min
  • How to Diagnose a Silent Memory Leak

    Memory leaks are the ghosts of server administration: invisible until your OOM killer reaps a production process at 3 a.m. In this episode, Lucas and Luna walk through a real case from a mid-sized ad-tech company where a 12-line Node.js script silently consumed 32 GB over six days. They explain how to spot the early signs using /proc/meminfo, why RSS vs. USS matters, and the one tool (valgrind's memcheck) that catches heap allocations your monitoring dashboard misses. By the end, you'll know exactly which three metrics to graph and what a slow-shrinking 'available' memory curve actually looks like. No theory — just the diagnosis sequence that separates good sysadmins from great ones.

    #MemoryLeak #LinuxSysadmin #ServerAdministration #Bash #NodeJS #Valgrind #OOMKiller #ProcMeminfo #HeapAllocation #SystemMonitoring #Technology #FexingoBusiness #BusinessPodcast #LinuxTips #DevOps #Observability #SiteReliability #Engineering

    Keep every episode free: buymeacoffee.com/fexingo

    11 min
  • Why Your SSH Key Setup Is Probably Wrong

    Episode 4 of Linux Server Admin looks at the single most common server authentication mistake: misconfigured SSH keys. Lucas and Luna walk through a real post-mortem from a fintech startup that left port 22 open with password authentication enabled for six months — not a breach, but a near-miss that triggered a full security audit. They break down SSH key anatomy, explain why 'ssh-keygen -t rsa -b 4096' is still fine but ed25519 is better, and show how a proper authorized_keys file with from= restrictions and command= rules could have prevented a supply chain attack. If you manage even one production server, this episode will change how you think about your ~/.ssh directory.

    #SSH #ServerSecurity #LinuxAdmin #OpenSSH #Ed25519 #KeyManagement #AuthorizedKeys #CyberSecurity #Fintech #DevOps #Sysadmin #Infrastructure #TechPodcast #Technology #FexingoBusiness #BusinessPodcast #Linux #ServerAdmin

    Keep every episode free: buymeacoffee.com/fexingo

    9 min
  • Why Your Server Needs A Dedicated Log Partition

    Episode 3 of Linux Server Admin with Fexingo: Sysadmin, Bash, and Server Engineering. Lucas and Luna dive into a classic sysadmin mistake: letting logs fill up the root partition. Lucas explains how unbounded logging by a single chatty service took down a mid-size e-commerce platform for three hours last year, and why a dedicated log partition with proper rotation is the fix. He walks through partitioning strategies, logrotate configuration, and the monitoring setup that alerts before disaster. Luna asks about trade-offs: smaller root partition risks, journald vs syslog-ng, and whether containers change the calculus. By the end, listeners learn why 'df -h' should be a daily habit and how a few hundred megabytes of planning can prevent a full outage.

    #Linux #Sysadmin #LogPartition #Logrotate #Journald #ServerEngineering #Bash #DevOps #Infrastructure #RootPartition #Logging #Ecommerce #Monitoring #DiskFull #ProductionOutage #Technology #FexingoBusiness #BusinessPodcast

    Keep every episode free: buymeacoffee.com/fexingo

    10 min
  • How Systemd Tamed Linux Boot Chaos

    Lucas and Luna dive into the story of systemd, the init system that replaced SysVinit and Upstart across nearly every major Linux distribution. They walk through the specific boot-time problem systemd solved—parallel service startup versus the old sequential model—and unpack a concrete example: how a modern Fedora system boots from UEFI to a login prompt in under 10 seconds while an equivalent SysVinit system took 45. They discuss the controversy around systemd's monolithic design, the role of socket-based activation for lazy service startup, and what happens when a unit file goes wrong. By the end, you'll understand why systemd is both loved and loathed, and how it fundamentally changed Linux server engineering. No fluff, just the mechanics.

    #Linux #Systemd #SysVinit #Upstart #BootProcess #InitSystem #ServerAdmin #Sysadmin #Bash #ServiceManagement #UEFI #ParallelStartup #SocketActivation #UnitFile #Technology #Podcast #FexingoBusiness #BusinessPodcast

    Keep every episode free: buymeacoffee.com/fexingo

    14 min
  • How a Five-Dollar Typo Broke a Production Server

    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

    13 min

About Linux Server Admin with Fexingo: Sysadmin, Bash, and Server Engineering

From the publisher's feed

Lucas and Luna sit down at a pair of thin laptops, terminal windows flickering with abstract patterns, to talk Linux server administration as it's actually practiced—bash scripting, systemd quirks, Nginx tuning, SSH hardening, and the daily grind of keeping production services online. Each episode picks a single sysadmin problem: how to diagnose a slow database query without panic, why that cron job keeps failing at 3 AM, or the right way to automate backups with rsync and rclone. Lucas brings the journalistic rigor—he'll cite real-world incidents like the 2021 AWS Kinesis outage that broke monitoring for half the internet, or the time a misplaced chmod command took down a major e-commerce site for an hour. Luna pushes back with hands-on experience: she's the one who asks whether you really need Docker for a three-service stack, or why your fail2ban config is banning your own IP. Together they cut through vendor hype—no Kubernetes if you have five servers, no Ansible if a shell loop will do—and focus on the tools and habits that keep systems boringly stable. The listener is someone who manages servers—maybe a solo IT generalist at a mid-size company, a DevOps engineer tired of conference talk, or a hobbyist running a home lab who wants professional-grade discipline. No whiteboarding abstract architectures; just concrete decisions, error messages, and the trade-offs between uptime and complexity. Can you afford to ignore SELinux? When is it smarter to reboot than to debug a memory leak? And how do you explain a 99.9% uptime SLA to a manager who thinks 'the cloud' fixes everything?