remote-spinloop

Fetching a Spinloop from a URL

Every other example in this directory is meant to be run in place — clone the repo, cd into it, spinloop apply. This one is different: the Spinloop and preset.ini here are meant to be published somewhere reachable over HTTP and consumed with a URL, not cloned. It's the same Qwen3.6-27B-on-llama.cpp setup as examples/llamacpp/qwen3.6-27b — see that example for the model itself, the llama-server prerequisites, and what the preset's flags do. This one is about the distribution of the file, not the model.

1. Publish the pair

spinloop fetches whatever's at the URL, so any static host works: a gist's raw URL, a GitHub raw URL (https://raw.githubusercontent.com/<org>/<repo>/<ref>/path/Spinloop), an internal artifact bucket, or — to try this locally — a plain file server from this directory:

cd examples/remote-spinloop
python3 -m http.server 8000

That serves Spinloop and preset.ini at http://localhost:8000/Spinloop and http://localhost:8000/preset.ini. Wherever it's actually published, the two files travel together — PRESET ./preset.ini in the Spinloop resolves relative to whatever URL fetched it, the same way it resolves against a local directory.

2. Apply it straight from the URL

spinloop apply http://localhost:8000/Spinloop

This fetches the Spinloop and applies it exactly as if it were a local file — no clone, no local copy. A URL ending in / is treated like a directory, so spinloop apply http://localhost:8000/ would fetch the same Spinloop too.

3. Give it a short name

Remembering a URL is worse than remembering a path. spinloop alias registers one under a name, exactly as it does for a local file:

spinloop alias -n qwen3.6-27b-team http://localhost:8000/Spinloop
spinloop apply qwen3.6-27b-team
spinloop serve qwen3.6-27b-team

Registering fetches the Spinloop once, to validate it — after that, the name works from any directory, on this machine.

4. Only serve fetches the preset

spinloop apply never reads PRESET — a local one or a URL, it's spinloop serve's business alone. Only running spinloop serve (or spinloop remote deploy) fetches http://localhost:8000/preset.ini:

spinloop serve qwen3.6-27b-team --dry-run   # fetches preset.ini, prints the command
spinloop apply qwen3.6-27b-team             # never touches preset.ini

Nothing here is fetched until the command that actually needs it runs — applying the Spinloop doesn't fetch the preset, and registering the alias doesn't either. See Fetching a Spinloop from a URL for the full picture, including the same rules for REMOTE.

See also

• examples/llamacpp/qwen3.6-27b — the same setup, run in place from a local clone
• spinloop alias — registering a name for a path or a URL