<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infrastructure on Shadowfish</title><link>https://shadowfish.night-tower.net/categories/infrastructure/</link><description>Recent content in Infrastructure on Shadowfish</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>© 2026 Creeping depths of the deep</copyright><lastBuildDate>Sat, 01 Aug 2026 19:00:00 +0200</lastBuildDate><atom:link href="https://shadowfish.night-tower.net/categories/infrastructure/index.xml" rel="self" type="application/rss+xml"/><item><title>The Great Database Wipeout: How a Single 'DROP DATABASE' Taught Me Everything About Backups</title><link>https://shadowfish.night-tower.net/post/the-great-database-wipeout/</link><pubDate>Sat, 01 Aug 2026 19:00:00 +0200</pubDate><guid>https://shadowfish.night-tower.net/post/the-great-database-wipeout/</guid><description>&lt;p&gt;There is a specific kind of cold sweat known only to software engineers and database administrators.&lt;/p&gt;
&lt;p&gt;It happens in a microsecond. You press &lt;strong&gt;Enter&lt;/strong&gt; in your terminal, expect a clean 3-millisecond query response, and instead watch the terminal freeze. You glance up at your tab title and realize with horror:&lt;/p&gt;
&lt;p&gt;You weren&amp;rsquo;t connected to &lt;code&gt;staging&lt;/code&gt;. You were connected to &lt;code&gt;production&lt;/code&gt;.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://shadowfish.night-tower.net/post/the-great-database-wipeout/featured.jpg"/></item><item><title>Inside Night-Tower: The Over-Engineered Homelab Powered by Fighter Jets and AI Chaos</title><link>https://shadowfish.night-tower.net/post/night-tower-homelab-architecture/</link><pubDate>Sat, 01 Aug 2026 13:30:00 +0200</pubDate><guid>https://shadowfish.night-tower.net/post/night-tower-homelab-architecture/</guid><description>&lt;p&gt;Most normal human beings buy a single-bay Synology NAS, plug it into their router, copy their family photos over, and call it a day.&lt;/p&gt;
&lt;p&gt;Then there are homelab enthusiasts.&lt;/p&gt;
&lt;p&gt;We look at a simple home network and think: &lt;em&gt;&amp;ldquo;You know what this single-bedroom apartment really needs? A three-node high-availability baremetal Proxmox hypervisor cluster, enterprise-grade OPNsense firewalling, automated GitOps CI/CD pipelines, local AI LLM orchestration, and 1Password-vaulted Ansible playbooks.&amp;rdquo;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Welcome to &lt;strong&gt;Night-Tower&lt;/strong&gt;—the homelab where enterprise-grade architecture meets absurd levels of over-engineering.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://shadowfish.night-tower.net/post/night-tower-homelab-architecture/featured.jpg"/></item><item><title>Standardizing Homelab IaC: Ansible Hostname Automation &amp; Zero-Trust VLAN Architecture</title><link>https://shadowfish.night-tower.net/post/homelab-ansible-vlan-segmentation/</link><pubDate>Mon, 27 Jul 2026 09:30:00 +0200</pubDate><guid>https://shadowfish.night-tower.net/post/homelab-ansible-vlan-segmentation/</guid><description>How I restructured my 3-node Proxmox VE cluster and containerized workloads using declarative Ansible playbooks and a Zero-Trust VLAN firewall strategy.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://shadowfish.night-tower.net/post/homelab-ansible-vlan-segmentation/feature.jpg"/></item></channel></rss>