lora-manager-runtime-context

The settings directory resolves in precedence order: the LORA_MANAGER_SETTINGS_DIR environment variable or --settings-path flag first, then portable mode via a repo-root settings.json with use_portable_settings enabled, then the default user config directory at ~/.config/ComfyUI-LoRA-Manager. The inspect script's summary subcommand prints the resolved path.

Open the databases read-only using SQLite URI modes mode=ro and immutable=1, which the bundled script does automatically. If a database is locked, the script copies it to a temporary directory and inspects the copy instead, so the live cache is never modified.

Model metadata lives next to each model file as a sidecar named <model basename>.metadata.json. The model subcommand of the inspect script accepts a model file path and summarizes the corresponding metadata JSON with sensitive values redacted.

No. The script redacts any settings key matching key, token, secret, password, auth, or credential patterns, including civitai_api_key, before printing. Redaction applies recursively to settings, JSON summaries, and sampled SQLite rows.

Caches are per-library: model, recipe, and model-update SQLite files are named after the sanitized active library under the cache directory. Check the active_library value in settings.json and confirm you are reading the matching <library>.sqlite files.

Yes. Pass --settings-path DIR (or set LORA_MANAGER_SETTINGS_DIR) to any subcommand to pin the entire settings directory, bypassing portable mode and the default config location. This is the standard approach for sandboxed or end-to-end test instances.