Simple homelab infrastructure management. ~250 lines of Babashka.

• EDN is the source of truth - services and integrations in one config
• Don't reinvent Docker Compose - generate YAML, pipe to docker compose -f -
• No temp files - YAML is ephemeral, piped via stdin, never written to disk
• Integrations are the value - automations between services

# 1. Install Babashka (if needed)
# macOS: brew install borkdude/brew/babashka
# Linux: curl -sLO https://raw.githubusercontent.com/babashka/babashka/master/install && bash install

# 2. Setup secrets
cp secrets.edn.example secrets.edn
vim secrets.edn

# 3. Run
./lab plan     # See generated docker-compose.yml
./lab up       # Start services
./lab status   # Check what's running
./lab down     # Stop everything

Services:

• Mealie - Recipe management and meal planning
• Donetick - Chore/task tracking

Integrations:

• meal-prep-reminder - Checks tomorrow's meals for prep notes (e.g., "prep:defrost salmon"), creates chores in Donetick
• mealie-weekly-list - Creates weekly shopping list from meal plan

Everything lives in config.edn:

{:secrets #include "secrets.edn"

 ;; Services → docker-compose.yml
 :services
 {:mealie {:image "ghcr.io/mealie-recipes/mealie:v3.10.2"
           :ports ["9925:9000"]
           :env {:BASE_URL #ref [:secrets :mealie-url]}}

  :donetick {:image "donetick/donetick"
             :ports ["2021:2021"]
             :env {:DT_JWT_SECRET #ref [:secrets :donetick :jwt-secret]}}}

 ;; Integrations → automations
 :integrations
 {:meal-prep-reminder
  {:handler "integrations/meal-prep-reminder.clj"
   :description "Cross-service: Mealie -> Donetick"}}}

Two types of integrations:

1. HTTP calls - Simple webhooks/API requests defined in EDN
2. Code handlers - Complex logic in Clojure files

Run manually:

./lab run meal-prep-reminder

Or schedule via cron:

crontab -e
# Add: 0 8 * * * /opt/lab/lab run meal-prep-reminder

Full documentation in docs/:

• Tutorial - Set up from scratch, run your first integration
• How-to Guides:
  • Run on Schedule - Cron and systemd timers
  • Write an Integration - Create your own automation
  • Deploy to Server - Production deployment
• Reference:
  • Configuration - Full config.edn schema
  • CLI Commands - All commands
• Architecture - Design decisions and tradeoffs

./test.sh unit         # Fast unit tests (~1s)
./test.sh integration  # Integration tests with mocks
./test.sh e2e          # Real containers - Mealie + Donetick (~90s)
./test.sh all          # Everything

# On your VPS/homelab server:

# 1. Install Babashka
curl -sLO https://raw.githubusercontent.com/babashka/babashka/master/install
sudo bash install

# 2. Clone/rsync your config
rsync -avz --exclude secrets.edn ./ user@server:/opt/lab/

# 3. On server: setup secrets and run
cd /opt/lab
cp secrets.edn.example secrets.edn
vim secrets.edn
./lab up

Edit config.edn:

:services
{:new-service
 {:image "nginx:latest"
  :ports ["80:80"]
  :volumes ["./html:/usr/share/nginx/html:ro"]
  :restart "unless-stopped"}}

Then: ./lab up

Simple HTTP call:

:integrations
{:notify-on-backup
 {:type :http-call
  :action {:method :post
           :url #ref [:secrets :webhook-url]
           :body {:text "Backup completed"}}}}

Code handler (for complex logic):

:integrations
{:meal-prep-reminder
 {:handler "integrations/meal-prep-reminder.clj"
  :description "Check meal plan, create prep chores"}}

Handler files receive config and return :ok or :error:

;; integrations/my-handler.clj
(fn [{:keys [secrets]}]
  ;; your logic here
  :ok)

Run: ./lab run meal-prep-reminder

Body templates: Use :current-date in :body for "Feb 18, 2026" format.

The tradeoff: v2 delegates reconciliation to Docker Compose. You lose the custom plan diff, but gain simplicity and battle-tested container management.