________ _______ ___ ___ ________ ________ ________ ________
|\ ___ \|\ ___ \ |\ \ / /| |\ __ \|\ __ \|\ ____\ |\ __ \
\ \ \_|\ \ \ __/|\ \ \ / / /___________\ \ \|\ \ \ \|\ \ \ \___|_ \ \ \|\ \ /\
\ \ \ \\ \ \ \_|/_\ \ \/ / /\____________\ \ \\\ \ \ ____\ \_____ \ \ \__ \/ \
\ \ \_\\ \ \ \_|\ \ \ / /\|____________|\ \ \\\ \ \ \___|\|____|\ \ \|_/ __ /|
\ \_______\ \_______\ \__/ / \ \_______\ \__\ ____\_\ \ / /_|\ / /
\|_______|\|_______|\|__|/ \|_______|\|__| |\_________\ /_______ \/
\|_________| |_______|\__\
\|__|
________ ___ ___ _________ ________ _____ ______ ________ _________ ___ ________ ________
|\ __ \|\ \|\ \|\___ ___\\ __ \|\ _ \ _ \|\ __ \|\___ ___\\ \|\ __ \|\ ___ \
\ \ \|\ \ \ \\\ \|___ \ \_\ \ \|\ \ \ \\\__\ \ \ \ \|\ \|___ \ \_\ \ \ \ \|\ \ \ \\ \ \
\ \ __ \ \ \\\ \ \ \ \ \ \ \\\ \ \ \\|__| \ \ \ __ \ \ \ \ \ \ \ \ \\\ \ \ \\ \ \
\ \ \ \ \ \ \\\ \ \ \ \ \ \ \\\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \\\ \ \ \\ \ \
\ \__\ \__\ \_______\ \ \__\ \ \_______\ \__\ \ \__\ \__\ \__\ \ \__\ \ \__\ \_______\ \__\\ \__\
\|__|\|__|\|_______| \|__| \|_______|\|__| \|__|\|__|\|__| \|__| \|__|\|_______|\|__| \|__|
-
Dev Platform: Git Service, Automation, Monitoring, and App Runtimes
I rebuilt my dev box so it behaves like a real platform instead of a pile of pets. The stack lives the same two-node Proxmox cluster I’ve been using. The controller node runs GitLab CE and a few utilities. The second node is a dedicated DevBox where I build and…
-
Yes, You Can Code on an iPad: VS Code Server + Cloudflare + OpenAI
People love to say “you can’t develop on an iPad.” Cute take. I’m happily writing, linting, testing, and committing from a 2nd-gen 11” iPad Pro because the browser is just a window, and my homelab does the heavy lifting. The trick… run VS Code Server in the lab, publish it…
-
2-Node Proxmox + 3-Node k3s, GitLab, and Backups
The first diagram is the “steel and wires” view: two Proxmox hosts on your 192.168.1.0/24 LAN, each carrying a tidy stack of VMs. pve2 is the busy one, home to the k3s control-plane (r9-ctrl at .30), the first worker (r9-node1 at .31), and your standalone GitLab VM (r9-gitlab at .45…
-
1 Control / 2 Worker k3s on Rocky
I set up a three-node k3s cluster on Rocky Linux 9: one control plane (r9-ctrl, 192.168.1.30) and two workers (r9-node1 192.168.1.31, r9-node2 192.168.1.32). The goal was a light, repeatable Kubernetes base I can manage from my Mac without babysitting VMs. Everything lives on my LAN, no cloud necessary. All three…