A command-line tool for managing Cooklang recipes, generating shopping lists, and serving a web interface from a single binary.
CookCLI is a command-line tool for managing recipes written in Cooklang, a plain-text markup language for cooking. It helps users create shopping lists, plan meals, track pantry inventory, and serve recipes via a web interface, all from the terminal. The tool automates cooking and shopping routines by integrating with existing UNIX command-line workflows.
Home cooks, meal planners, and developers who prefer command-line tools and want to manage recipes, generate shopping lists, and automate meal planning using a plain-text format.
CookCLI offers a unified, scriptable solution for recipe management that combines a CLI with a web server in a single binary. Its adherence to the UNIX philosophy allows seamless integration with other tools, while features like pantry tracking and aisle-based shopping lists provide practical automation for cooking and shopping.
Recipe Management CLI + embedded web-server in one binary
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Designed to do one thing well and integrate with pipes and scripts, as shown in the Tips section with examples like using xargs to chain search and shopping-list commands.
Automatically combines ingredients from multiple recipes and categorizes them by store aisle using configurable aisle.conf files, reducing manual effort in list creation.
Includes a built-in web server with a functional UI for browsing recipes from any device on the local network, demonstrated in screenshots and the demo site.
Manages ingredient inventory with expiration dates and low stock thresholds, automatically excluding pantry items from shopping lists to minimize waste and overbuying.
Building from source requires Rust and Node.js, plus npm commands to compile CSS for the web UI, adding unnecessary steps compared to binary installation.
The import command relies on an OpenAI API key, making it dependent on external paid services and potentially limited or costly for frequent use.
Optimal use requires manually creating and maintaining aisle.conf and pantry.conf files, which can be tedious and error-prone for users with large or diverse recipe collections.