Deploying Proxmox VE on a Hetzner dedicated bare metal server with a single public IP can be challenging because Hetzner does not provide standard IPMI/KVM access out of the box unless requested.
In this guide, we will walk through the step-by-step process of downloading Proxmox VE 9.x, installing it via QEMU inside the Hetzner Rescue System using a ZFS RAID0 layout for maximum performance across two disks, configuring native SDN-based NAT, and setting up Tailscale for secure remote management.
In my previous post, we set up Proxmox VE on a Hetzner dedicated server. While the installation is complete, accessing the Proxmox dashboard usually involves opening port 8006 to the public internet or using a VPN. A more modern and secure approach is to use Cloudflare Tunnels (Cloudflared). This allows you to access your dashboard via a nice hostname (e.g., proxmox.yourdomain.com) without opening any inbound ports on your server.
Why Cloudflare Tunnels? # No Inbound Ports: You can keep your firewall completely closed to the public internet. Identity-Based Access: You can add Cloudflare Access rules (SSO, 2FA) in front of your Proxmox login. Automated SSL: Cloudflare handles the SSL/TLS certificates automatically. 1. Prerequisites # A Proxmox VE server (see the installation guide). A domain managed by Cloudflare. A Cloudflare Zero Trust account (Free tier is fine). 2. Setting Up the Tunnel in Cloudflare Dashboard # Log in to the Cloudflare Dashboard. Navigate to Zero Trust > Networks > Tunnels. Click Create a tunnel and name it (e.g., proxmox-hetzner). Select Cloudflared as the connector. Choose your environment (e.g., Debian 64-bit). 3. Installing Cloudflared on Proxmox # Back in your Proxmox terminal, follow these steps to install the agent:
Deploying Proxmox VE on a Hetzner Dedicated Server can be a bit tricky due to Hetzner’s specific network security policies. In this guide, we will walk through the process of installing Proxmox VE on a fresh Debian 13 (Trixie) installation and configuring a modern, scalable networking stack using Software-Defined Networking (SDN).
If you are looking to expose your Proxmox dashboard securely without opening ports, check out my follow-up guide: Securing Proxmox VE with Cloudflare Tunnel.
Managing my developer environment across multiple machines (macOS, Ubuntu, Oracle Linux, and minimal Docker containers) has always been a challenge. Most dotfiles setups I’ve seen rely on brittle helper scripts, global sudo installations, or manual token handling.
I decided to fix this by building a fully native, no-sudo, and secure dotfiles infrastructure from the ground up. Here’s how I modernized my workflow and why it’s a game-changer for my daily productivity.
I am in the middle of a career shift.
For years, I worked close to legacy database systems. That experience taught me how to think carefully, solve production problems, and respect reliability.
Now I am moving toward platform engineering.
To make that shift visible and real, I started a public GitHub repository:
legacy-dba-to-platform-engineer
This repository is my working log. I will use it to document what I learn, what I build, and how my thinking changes over time.
This guide provides the official, recommended steps to configure a custom subdomain (e.g., blog.savdert.com) for GitHub Pages using Cloudflare as your DNS provider, based on GitHub’s official documentation.
1. Configure GitHub Pages # First, you need to tell your GitHub repository that you intend to use a custom domain.
Navigate to your GitHub repository.
Go to Settings > Pages (under the “Code and automation” section).
Pigsty is an open-source, battery-included PostgreSQL distribution that allows you to self-host PostgreSQL databases like a professional RDS (Relational Database Service). Developed by Vonng, Pigsty provides a comprehensive platform for deploying, managing, and monitoring PostgreSQL clusters with enterprise-grade features.
What is Pigsty? # Pigsty stands for “PostgreSQL In Great STYle” and encompasses Postgres, Infrastructure, Graphics, Service, Toolbox, and more. It’s designed to make PostgreSQL deployment as easy as possible while offering advanced capabilities that rival commercial database services.
Building a fast, lightweight, and modern developer blog doesn’t have to require heavy server infrastructure or database systems. In this article, I will walk you through the exact technical details of how this blog was initialized, customized, and automated using Hugo, the Blowfish theme, Git submodules, and GitHub Actions.
The Core Stack # Static Site Generator: Hugo (known for being incredibly fast to build). Theme: Blowfish (a highly configurable, responsive, and aesthetically premium Hugo theme built with Tailwind CSS). Hosting & CI/CD: GitHub Pages deployed automatically via a GitHub Actions workflow. Step 1: Repository Initialization & GitHub Setup # To build a personal site hosted on GitHub Pages, we start by duplicating a starter template.
Welcome to my new technical blog! Here, I will be sharing guides, architectural insights, and hands-on tutorials about platform engineering, cloud-native deployments, database administration, and automating complex systems.
What We Will Cover # In-depth technical articles on the following domains:
Platform Engineering: Building internal developer platforms (IDPs), Infrastructure as Code (IaC) patterns, and developer self-service tools. Kubernetes: Cloud-native architecture, container orchestration, scaling, ingress management, and operators. DevOps & CI/CD: Software delivery pipelines, automating GitOps workflows (e.g., ArgoCD, Flux), and security scanning. Database Administration (DBA): Designing high-availability database architectures, automated backups, performance tuning, and database reliability engineering. Stay tuned for upcoming deep dives!