Self-Hosting Cooklang and Integrations with Other Tools

Because Cooklang is files plus a CLI, self-hosting it is mostly trivial: a folder, a git repo, and any web server is already a deployment. The interesting work is in the integrations — connecting Cooklang to the rest of your kitchen-tech stack: a Home Assistant dashboard, a Raspberry Pi mounted on the fridge, a mobile app that syncs your recipes between devices, or a programmatic API in another application.

For the simple setup, Self-Hosting Recipes with Docker walks through a containerised CookCLI server. For something more ambitious, Raspberry Pi Kitchen Display covers wall-mounted recipe screens, and Cooklang Home Assistant Smart Kitchen integrates recipes into an existing home-automation setup.

On the application side, Cooklang Mobile App covers the official iOS/Android client, while Desktop App Replaced by Sync Agent explains why we moved away from a desktop app and what the sync agent does instead. The File Sync Library post is the technical story behind that move.

For developers, Building a Recipe API with Cooklang walks through embedding Cooklang in your own backend, and A Plain Text Recipe Database explains how the filesystem itself acts as the database layer — no Postgres required.

A common pattern across all of these: the integration is usually a thin shim. CookCLI does the parsing and the data shaping; the integration is just a script or a small service that hands files in and gets structured output back. If you find yourself building anything elaborate to hold Cooklang together, it's usually a sign there's a simpler path.