Tech Musings
Tech Musings
Why DietPi?
DietPi is a great introduction to Linux for the budding SBC enthusiast. It allows you to get a SBC up and running with a minimal Deb-Ian OS and simplifies the install of server applications. Once a system is running you can become more comfortable with the CLI Command Line Interface. The learning curve is less steep than doing self installs of a Linux OS and software.
Power Supplies
The first steps for building a home server system should include getting a battery back-up UPS Uninteruptable Power Supply for your internet modem/router and Pi servers. You need one anyway, what good is a laptop with battery if power glitches bring down your internet connection and you have a five minute wait while it reboots and reconnects to the internet during an important Zoom call. Also unnoticed power glitches play havoc with diagnosing mysterious server crashes. I have also found that SBCs reboot quicker than my modem/router and the reboot often fails if there is no network connectivity.
Speaking of power for SBCs, I have found that cheap power supplies, even if they have power ratings that seem adequate can cause mysterious no-boots or crashes. It is best to stick with Raspberry Pi branded power supplies. If needed, use USB hubs that have their own power supply. The power draw of a hub or hard disk plugged directly into a SBC can prevent booting.
USB and HDMI Adapters
USB-C has introduced adapter mayhem into our lives. Make sure you have a variety of USB adapters. USB-A to USB-C, HDMI adapters, etc. When ordering a SBC read the specifications to ensure you have the needed adapters on hand. Note that the USB ports on SBCs are often close together and fat (wide) adapters may not fit.
HomeLab?
If you are going to have a home media/file/VPN/... server I suggest the following.
Multiple simple Pi servers! The name of the game is up-time. I want my file server running for months witthout attention. Get one service running reliably. Add a second server to your network for the next service. One service - one server. But isn't that wasteful? I find that getting a service/server running reliably is easier than running several services on one server.
First server = Multiuser File Server
Start simple, start small. I suggest that your first server should be a simple Samba file server with a commodity 1 or 2 TB SSD. Keep the factory format, do not reformat. When I am dead and gone, my heirs should be able to plug my file archive SSD into any computer without having anything to worry about, except a file access username:password printed directly on the SSD.
Why SSD? A SSD draws less power than a hard drive and can be plugged directly into a Pi without worry that it will be a power management issue.
Why Samba? Tried and true. I can access from Mac, Windows, Linux, android phone ... also I can have multiple users access the same file server.
Why USB SSD factory format (FAT-NTSC)? I can plug it into Mac, Windows, Linux ...
Why not an NAS? Start simple. The second server you set-up will be for backup. Plus I feel like the time I spend learning how to navigate a third party's admin I would spend learning about Pis and Debian. I find that a simple nightly backup to a second Pi using rsync over ssh and cron jobs suits my needs. Sure, it is not as sexy as a powerful NAS with multi terrabyte hard drives, but I prefer simple, that I understand.
Why not Docker? Start simple. It seems like another layer of complication. If you are only running one or two services per server/Pi there is no need for Docker.
Second server = Backup Server