SEC.01
The playbook
The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.
- 01reconHomebrew present? absolute path, prefix owner (brew refuses root: go through sudo -u <owner>), architecture
- 02reconOllama already present (formula or Ollama.app)?
- 03reconport 11434 free?
- 04reconRAM and free disk (a 3B model ≈ 2 GB, 8B ≈ 5 GB)
- 05actInstall Ollamaverify
- 06actStart the serviceverify
- 07actDownload the model (only if a model is provided)verify
SEC.02
What it verifies
Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.
- 01verifyInstall OllamaVerified by
b=$(ls /opt/homebrew/bin/brew /usr/local/bin/brew 2>/dev/null | head -1); u=$(stat -L -f %Su "$b"); p=$(dirname "$(dirname "$b")"); "$p/bin/ollama" --version - 02verifyStart the serviceVerified by
curl -sf http://127.0.0.1:11434/api/version - 03verifyDownload the model (only if a model is provided)Verified by
b=$(ls /opt/homebrew/bin/brew /usr/local/bin/brew 2>/dev/null | head -1); u=$(stat -L -f %Su "$b"); p=$(dirname "$(dirname "$b")"); "$p/bin/ollama" list | grep -c "${model}"
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
If Homebrew is missing, stop and suggest the install-homebrew recipe. The API stays on 127.0.0.1:11434: do not set OLLAMA_HOST=0.0.0.0. Announce the model size before pulling and check disk space.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${model} | Model to pull (optional) |
SEC.05
How a recipe runs in Servor
Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.06
Deploy on Servor button
Maintain Ollama (macOS) or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.
SEC.07
More ai / ml recipes
- 01OllamaOllama to run local LLMs (NVIDIA GPU if present, CPU otherwise), API on 127.0.0.1, optional model pull.
- 02JupyterLabJupyterLab via Docker, on 127.0.0.1 with a generated access token (access through an SSH tunnel).
- 03Open WebUIOpen WebUI, a web interface for LLMs (Ollama), via Docker on 127.0.0.1, wired to the local Ollama.
- 04NVIDIA drivers + CUDANVIDIA driver, CUDA toolkit and Docker Container Toolkit from the official repositories. Destructive: kernel modules, restart likely.
- 05ComfyUI (Stable Diffusion)ComfyUI for image generation, installed from the official repository as a systemd service (NVIDIA GPU recommended, CPU possible).
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.