mirror/LocalAI
1
0
Fork 0
mirror of https://github.com/mudler/LocalAI.git synced 2026-06-20 14:49:09 -04:00
Code Issues Packages Projects Releases Wiki Activity

fix: correct alias conversion docs and advertise /api/aliases in instructions

Browse Source 
Signed-off-by: Ettore Di Giacinto <mudler@localai.io>
This commit is contained in:
Ettore Di Giacinto
2026-06-20 10:42:52 +00:00
parent 32a42c50d8
commit 20196357c4
2 changed files with 12 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
core/http/routes/localai.go
View File

@@ -306,6 +306,7 @@ func RegisterLocalAIRoutes(router *echo.Echo,
"edit": "/models/edit/:name",
"import": "/models/import",
"reload": "/models/reload",
"list_aliases": "/api/aliases",
},
"ai_functions": map[string]string{
"tts": "/tts",

18
docs/content/features/model-aliases.md
View File

@@ -60,14 +60,18 @@ The LocalAI Assistant (and the MCP server) expose the same operations as tools:
`set_alias`, `list_aliases`, and `delete_model`.
{{% notice note %}}
**Pointing at an existing real model converts it into an alias.** If you run
`set_alias` (or `PATCH /api/models/config-json/:name`) against a name that is
already a real, non-alias model, that model is turned into an alias of the
target. The operation is non-destructive (no data is deleted), but the model
stops serving with its own backend and starts redirecting to the target.
**You cannot turn an existing real model into an alias.** If you run `set_alias`
(or `PATCH /api/models/config-json/:name`) against a name that is already a real,
non-alias model, the request is **rejected**. An alias is a pure redirect, so it
must not carry a `backend` or `parameters.model`; a real model does, and merging
an `alias` onto it produces an invalid config that validation refuses with
`alias config ... must not set backend or parameters.model`. This is intentional:
it stops a stray `set_alias` call from clobbering a model that is serving.
If you want to keep the original model serving as-is, point a **new** name at
the target instead of reusing an existing model's name.
To add an alias, point a **new** name at the target instead of reusing an
existing model's name. Re-pointing an **existing alias** at a different target
is fully supported and is the live-swap path: the alias config has no backend of
its own, so swapping its target stays a valid pure redirect.
{{% /notice %}}
## Limits