docs: document POST /models/reload under model management - #11656
Closed
pos-ei-don wants to merge 1 commit into
Closed
docs: document POST /models/reload under model management#11656pos-ei-don wants to merge 1 commit into
pos-ei-don wants to merge 1 commit into
Conversation
`/models/reload` is currently mentioned only in `operations/middleware.md`, in the context of router configs. Someone managing models reads `advanced-usage.md`, finds only `/models/apply` — which downloads from a gallery definition — and concludes that a locally written YAML needs a restart. This adds the endpoint next to `/models/apply` and states the difference. It also records a limit that is documented nowhere and is easy to get wrong: reloading adds new configurations and replaces changed ones, but does not drop a configuration whose file was deleted. That entry stays in `/v1/models` until restart. Verified against a running v4.7.1: adding an alias config and re-pointing an existing one both took effect after /models/reload; deleting the file did not remove the entry. Also adds the `alias` field to the model config field table, linking to the existing Model Aliases page. Assisted-by: Claude:claude-opus-5
pos-ei-don
force-pushed
the
docs/runtime-reload-and-aliases
branch
from
August 21, 2026 09:20
3393ae0 to
127d005
Compare
localai-org-maint-bot
requested changes
Aug 21, 2026
localai-org-maint-bot
left a comment
Collaborator
There was a problem hiding this comment.
The documentation matches the endpoint implementation and current additive reload behavior. The alias field and link are also accurate. The only blocker is DCO: the commit lacks a human Signed-off-by trailer, and the DCO check fails. Please amend the commit with your own sign-off and force-push it. I cannot add that attestation for you.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
POST /models/reloadto the model-management docs, plus one missing row in the model config field table./models/reloadis currently mentioned only inoperations/middleware.md, in the context of router configs. Someone managing models reads Advanced usage → Install models using the API, finds only/models/apply— which installs from a gallery definition and downloads files — and concludes that a locally written YAML needs a restart. This puts the endpoint next to/models/applyand states the difference.It also records a limit that is documented nowhere and is easy to get wrong: reloading adds new configurations and replaces changed ones, but does not drop a configuration whose file was deleted — that entry stays in
/v1/modelsuntil restart.The second hunk is a single row adding
aliasto the field table in the model configuration reference, linking to the existing Model Aliases page.Verified
Against a running v4.7.1, not inferred from the source: adding an alias config and re-pointing an existing one both took effect after
/models/reloadwithout a restart; deleting the file did not remove the entry.Docs only — no code changes.
Assisted-by: Claude:claude-opus-5 — per
CONTRIBUTING.md, I have reviewed the change and am responsible for it.