Headless Raspberry Pi Homelab – Part 1: OS Configuration & Remote Access
Source: Dev.to
Project Overview
This project documents the process of imaging and configuring a Raspberry Pi to function as a headless database server on a local network, with a focus on OS deployment, remote access, and preparing the system for headless database hosting and homelab expansion.
Hardware Used
- Raspberry Pi 4 Kit – Amazon link
- Uni SD Card Reader – Amazon link
- Samsung 32 GB EVO Plus microSD card – Amazon link
Installing the OS & Writing to the microSD Card
For the official step‑by‑step process, the Raspberry Pi Foundation provides documentation. I followed their guide while performing my own process.
Official Raspberry Pi Getting Started Documentation
Step 1: Install the Raspberry Pi Imager
Download and install the Raspberry Pi Imager for your operating system.
Official Raspberry Pi Imager Software
After installation, ensure the software is fully updated before proceeding.
Step 2: Select Device & Operating System
- Launch Raspberry Pi Imager.
- Select your Raspberry Pi model (I’m using a Raspberry Pi 4).
- Choose the Raspberry Pi OS (64‑bit is recommended).
Why 64‑bit?
The 64‑bit OS provides better memory handling and compatibility with modern services such as databases and containerised applications.
Step 3: Prepare the Storage Device
The Samsung microSD card and adapter.
Insert the Samsung microSD card and adapter into the Uni SD Card Reader.
Connect the storage device to your computer.
Once connected and granted access, the storage device should appear in the Select Storage menu of the Imager.
Step 4: Configure OS Customisation Settings
Before writing the OS, the Raspberry Pi Imager allows several important pre‑boot configurations.
Hostname
Set a custom hostname to easily identify the device on the network.
Localization
Configure the timezone and keyboard layout based on your geographical location.
Username & Password
Create a user account that will be used for SSH access.
Step 5: Network & Access Configuration
Wi‑Fi (Optional)
The Wi‑Fi setup was skipped in favor of Ethernet.
Why Ethernet?
- More stable connection
- Lower latency
- Easier to troubleshoot
- Common practice in server environments
SSH
SSH was enabled during imaging using password authentication.
This ensures the Pi can be accessed remotely without requiring a display.
Step 6: Raspberry Pi Connect (Optional)
Raspberry Pi Connect provides secure remote‑access features. Since this was new to me, I enabled it to explore its capabilities.
If you choose to enable Raspberry Pi Connect, you’ll need to create an account and verify it.
Step 7: Write the OS Image
After reviewing all customizations, proceed with writing the OS to the microSD card.
Warning: This process erases all existing data on the microSD card.
When the writing process finishes, the Write Complete page appears. Click Finish, then.