Files

pasture keeps its settings, state, and logs in these files:

Path	What it holds
~/.config/pasture/config.json	The budget, reserve, pins, archive folder, allowed web origins, Ollama variables, and the keys you edit by hand.
~/.config/pasture/node.json	This machine's pairing: its node id, its node key, and the link address. Only you can read it.
~/.config/pasture/keys.json	A hash of each API key, never the key. Only you can read it.
~/.local/state/pasture/certs	The HTTPS certificates and the Let's Encrypt account key.
~/.local/state/pasture/state.json	When each model was last used, and the moved-away models.
~/.local/state/pasture/state.json.bak	The state before its last change.
~/.local/share/pasture/ollama/<version>	The Ollama that pasture downloaded, when no ollama command was installed.
~/.local/state/pasture/token	The admin token for pasture's own commands, new each time pasture starts.
~/Library/Logs/pasture.log	The log of pasture and ollama serve, on macOS. It starts a new file at 10 MB and keeps three.
~/Library/Logs/pasture-crash.log	What pasture prints outside its log, such as a crash, on macOS.
~/Library/LaunchAgents/com.cinchapi.pasture.plist	The launchd job, on macOS.
~/.config/systemd/user/pasture.service	The systemd unit, on Linux.

On Linux, the systemd journal holds the log. Read it with journalctl --user -u pasture.

A damaged state file

pasture puts state.json on the disk before it goes on. When the file is damaged anyway, pasture moves it to state.json.bad, starts from state.json.bak, and logs what it did.

Other locations

PASTURE_CONFIG and PASTURE_STATE name other files for the config and the state. The token file is in the state file's folder.