Overview
Pi Picker is a project I started to address the common issue of finding incomplete or outdated information when building with Raspberry Pis. The idea is to start from what you want to build—like a Pi-hole ad blocker, home server, NAS, or learning environment—and get a verified parts list along with real compatibility warnings.
Background
The inspiration for this project came from my own experiences with inconsistent and out-of-date information online. I wanted a tool that could provide goal-first guidance rather than part-first advice. The goal is to create a database of verified builds and compatibility information, backed by practical experience in my homelab.
How It Works
Planning Phase
The project is still in the early planning stage. Key aspects include:
- Goal Selection: Define specific goals for builds (e.g., Pi-hole ad blocker, home server).
- Part List Verification: Create a parts list that works with the chosen goal.
- Compatibility Testing: Test the build to ensure everything works as expected.
Current Status
- A handful of Raspberry Pis are already in use:
- Raspberry Pi 5 8GB boards: Running Pi-hole for network-wide ad blocking, retro game emulation, and an AI-assisted camera tracking project.
- Raspberry Pi 4 4GB: Used for smart home automation.
These builds serve as the foundation for the initial guide content. The first step is to write up and publish a few goal-first build guides based on these existing setups.
Feature Ladder
The next steps involve:
- Picking Goals: Selecting the first 1-2 goals to document.
- Writing Guides: Creating detailed guides for each selected goal.
- Verification: Ensuring all parts and configurations work as expected before publishing.
Results
At this stage, there are no concrete results to report since the project is still in the planning phase. However, the initial setup of my homelab provides a solid foundation for testing and verifying builds.
Lessons Learned
- Start Small: Begin with simple goals that can be quickly verified.
- Iterate Based on Feedback: As more guides are written, refine the process based on user feedback.
- Maintain Objectivity: Ensure that any affiliate links or monetization strategies do not compromise the tool's utility.
TODO:
- Define the first 1-2 goals for initial build guides.
- Write up and test the selected builds.
- Document the verification process in detail.