CookCLI
Self-HostedOpen-source CLI tool for local recipe management
Overview
CookCLI is a lightweight, terminal-native recipe manager for command-line enthusiasts. Store, search, and organize recipes locally—no cloud sync or server required. Features include tag-based categorization, ingredient lists, step-by-step instructions, and batch imports/exports (JSON/plain text). Install via pip or GitHub source; works on Linux, macOS, Windows (WSL/PowerShell). Ideal for users valuing offline access, full data control, and fast keyboard-driven workflows with minimal overhead.
Self-Hosting Resources
Below is a reference structure for docker-compose.yml.
⚠️ Do NOT run blindly. Replace placeholders with official values.
version: '3'
services:
cook_cli:
image: <OFFICIAL_IMAGE_NAME>:latest
container_name: cook-cli
ports:
- "8080:<APP_INTERNAL_PORT>"
volumes:
- ./data:/app/data
restart: unless-stopped Key Features
- Local-first offline storage
- Fast CLI search & filtering
- Tag-based recipe organization
Frequently Asked Questions
? Is CookCLI hard to install?
No—CookCLI can be installed quickly via pip (Python package manager) with a single command, or built from source using its GitHub repo. It has minimal dependencies (Python 3.8+) and runs on Linux, macOS, and Windows (via WSL or PowerShell).
? Is it a good alternative to Paprika Recipe Manager?
Yes, if you prefer CLI over GUI and value local data control. Unlike Paprika (cloud-synced), CookCLI stores recipes offline. It lacks Paprika’s visual features but offers faster search and no recurring costs.
? Is it completely free?
Yes—CookCLI is open-source under the MIT License. All core features are free, with no hidden fees or premium tiers. You can modify or contribute to the codebase on GitHub.
Top Alternatives
People Also Ask about CookCLI
Tool Info
Pros
- ⊕ Privacy-focused (no cloud dependency)
- ⊕ No subscription fees
Cons
- ⊖ CLI-only (no GUI option)
- ⊖ Requires basic terminal knowledge