Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -158,6 +158,8 @@ Minimal `mizan-daemon.toml`:
control_plane_url = "http://127.0.0.1:18180"
daemon_token_path = "/run/secrets/mizan-daemon-token"
local_provider_url = "http://127.0.0.1:11434/v1"
# Optional for local providers that require bearer auth.
# local_provider_api_key = "local-secret"
provider_family = "openai-compatible"
advertised_models = ["llama3.1"]
max_concurrency = 2
Expand Down
2 changes: 2 additions & 0 deletions crates/mizan-daemon/Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,11 @@ rust-version.workspace = true
[dependencies]
clap = { version = "4", features = ["derive"] }
mizan-core = { path = "../mizan-core" }
mizan-providers = { path = "../mizan-providers" }

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Regenerate Cargo.lock for the daemon dependency changes

Adding this new daemon dependency without committing the matching Cargo.lock update leaves the lockfile's mizan-daemon entry without mizan-providers or the newly added uuid dependency. I checked cargo check --help, where --locked is documented as asserting that Cargo.lock remains unchanged, so locked/frozen or reproducible build environments will need to modify the committed lockfile and can fail; please regenerate and commit Cargo.lock with these new daemon deps.

Useful? React with 👍 / 👎.

reqwest.workspace = true
serde.workspace = true
serde_json.workspace = true
tokio.workspace = true
toml = "0.8"
tracing.workspace = true
uuid.workspace = true
Loading