Raspberry Pi

This section is for Raspberry Pi guides where the platform itself matters.

That distinction matters for the same reason it mattered in Proxmox.

General networking concepts should stay under Networking. General Pi-hole architecture should stay under Pi-hole In A Homelab. Proxmox-specific deployment steps should stay under Proxmox Workloads.

What belongs here is the Raspberry Pi execution layer: imaging the OS, hardening the box, managing its storage, and using it as a small always-on infrastructure node.

In This Section

• Pi-hole On Raspberry Pi 4B - build a dedicated Pi-hole node on Raspberry Pi OS Lite and handle the Pi-side backup, hardening, and HA tasks without duplicating the Proxmox deployment guide.
• JetKVM Admin Terminal On Raspberry Pi 3 - turn a Raspberry Pi 3 into a small browser-first admin terminal for JetKVM without turning it into another full workstation.

How To Use It

Read the pages below when the answer is either "this service belongs on a small dedicated Pi" or "this admin job is easier if a Pi lives near the rack and stays ready."

If you are still deciding where Pi-hole belongs in the network, start with Pi-hole In A Homelab first. If the page is really about the JetKVM device itself rather than the Pi client, start in JetKVM instead.