My Raspberry Pi Setup

This page documents my Raspberry Pi setup and how I use it to experiment with self-hosting, networking, and automation. It covers the hardware, DNS setup, software stack, and my motivations behind these choices.

🧩 Hardware

I currently own three Raspberry Pi 4 Model B boards, each with 4GB RAM and a 128GB SD card:

Main Pi – Always on, Ethernet-connected, used for hosting my personal websites and services.

Second Pi – Used for experimentation with VPNs, networking tools, or extra compute when needed.

Spare Pi – Currently not in use, kept as a backup.

🌐 Domains, DNS & VPN

I registered the fuselli.net domain via Aruba.it. Initially, I used DuckDNS to manage dynamic DNS updates while experimenting from a home connection. Later, I moved DNS to Cloudflare to gain more control, use proxy/CDN features, and simplify DNS automation.

I configured Tailscale to connect all my devices in a private mesh network (Tailnet), making it easy to access my Pis remotely and securely without port forwarding.

🧪 Use Cases & Services

My main use cases for the Raspberry Pis include:

Hosting static and dynamic websites (like luisaegreg.fuselli.net and rock-paper-scissors.fuselli.net)

Experimenting with networking setups (VPNs, DNS, proxies)

Learning and deploying small backend apps using Node.js/Express

I use Nginx as a reverse proxy to serve different sites and route requests properly. Some services are public, others are private and only accessible via the Tailnet.

🔄 Automation & Monitoring

Daily and weekly cron jobs for backups and log cleanup

Basic health checks to ensure services are alive

Future idea: a simple dashboard to manage hosted apps and monitor uptime

🔧 Tools & Services Used

Here are some of the key technologies and services that make everything work:

🔙 Back to Projects