Documentation
¶
Overview ¶
Package paths resolves every Ozy install location behind one abstraction so the installer and uninstaller never hardcode directories. It follows the conventions already used by internal/config (XDG config home) and internal/sidecar (state-dir venv): XDG-style locations on Linux and macOS, the %APPDATA%/%LOCALAPPDATA% conventions on Windows. Documented overrides (OZY_CONFIG and the XDG_* variables) take precedence.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
Types ¶
type Paths ¶
type Paths struct {
ConfigDir string // directory holding ozy.jsonc
ConfigFile string // ozy.jsonc path (honors OZY_CONFIG)
DataDir string // models / vector assets live under here
CacheDir string // disposable cache
StateDir string // durable runtime state (install state, logs, venv)
LogDir string // installer/uninstaller logs
VenvDir string // managed Python venv (passed to sidecar.Provision)
AssetDir string // downloaded embedding/vector assets
UserBinDir string // where the ozy binary is installed
BinaryPath string // resolved ozy binary path
}
Paths holds every resolved Ozy location. Consumers read these fields instead of recomputing or hardcoding paths.
Click to show internal directories.
Click to hide internal directories.