ARADR-002: Unified Nix + standalone configuration #4
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/llm-log#4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Make llm-log configurable through either Nix/Home Manager or a normal standalone config file without changing proxy semantics.
Auto-ARADR decision
Use one canonical runtime configuration model with two frontends:
services.llm-log.enable = truecreates the systemd user service and existing module options remain declarative.llm-log serveloads TOML from$XDG_CONFIG_HOME/llm-log/config.toml(fallback~/.config/llm-log/config.toml) when present;--config PATHselects an explicit file.CLI values override config-file values. Repeatable
--upstream NAME=URLentries override/add individual configured upstreams. Standalone capture data defaults to$XDG_DATA_HOME/llm-log(fallback~/.local/share/llm-log) so Nix and non-Nix defaults agree.The flake must continue exposing the package + Home Manager module and should expose a runnable app so
nix run ... -- serveworks without installation.RED-first acceptance
Before implementation, tests must fail proving the current CLI cannot:
Acceptance criteria
llm-log serve --config /path/config.tomlworks.services.llm-log.enable = trueand configurable systemd user service options.Non-goals
Closed as superseded by the zero-Python migration. The still-required Common Lisp config/CLI + Nix/non-Nix packaging contract is now owned by #10 under the #20 correction; the older Python-oriented implementation path should not be treated as canonical.