Raspberry Pi Kitchen Server
A Raspberry Pi running CookCLI serves your recipes to every device on your home network. No cloud, no subscription — just a $35 board drawing less power than a LED bulb.
What You Need
- Raspberry Pi 3B+ or newer (2GB+ RAM)
- MicroSD card (16GB+)
- Power supply and network connection
Quick Start
1. Prepare the Pi
Flash Raspberry Pi OS Lite to your SD card. Enable SSH and configure WiFi during imaging.
2. Install CookCLI
3. Add Recipes and Start the Server
Access from any device: http://raspberrypi.local:9080
Running as a Service
Create a systemd service so the server starts automatically and survives reboots:
Network Setup
Static IP
Reserve a consistent IP so your bookmark always works:
Mobile Access
Add a home screen shortcut on your phone:
- iOS: Safari > Share > "Add to Home Screen"
- Android: Chrome > Menu > "Add to Home screen"
Firewall
Syncing Recipes
Git
Version control your recipes and sync across devices:
Pull changes from other devices with a cron job:
Backups
Optional: Nginx Reverse Proxy
Serve on port 80 with caching and compression:
SD Card Optimization
Reduce write wear for longer card life:
What to Expect
- Page load: <100ms on local network
- Concurrent users: 10-15 comfortably
- Recipe capacity: 10,000+
- Power:
5W ($5/year electricity) - Cost: ~$75 for Pi 4 (2GB) + SD card + power + case
Troubleshooting
Can't connect from other devices: Check sudo ufw status — port 9080 must be allowed. Verify the Pi's IP with ip addr show.
Server stops when SSH closes: Use the systemd service above, or nohup cook server ~/recipes --host & as a quick fix.
Slow loading: Check SD card health with sudo hdparm -t /dev/mmcblk0 (should be >20 MB/sec). Monitor resources with htop.
Wrong architecture binary: Run uname -m to check — aarch64 needs the 64-bit binary, armv7l needs 32-bit.
See Also
- CookCLI Server Command — server configuration options
- Shopping Lists — generate lists from your recipes
- Meal Planning — plan weekly meals