2e14511fe2
The blog has a deep post for 4.8 and a history post that covers the earlier
releases at summary altitude, but nothing in between. These five fill that
gap in the same shape as what-landed-in-localai-4-8: what the release was
for, runnable examples, and the limits that apply.
Every endpoint, CLI flag, env var and gallery entry is verified against the
matching release tag rather than taken from the release notes. That caught
two paths the published 3.10.0 notes got wrong: tracing is /api/traces, not
/api/v1/trace, and a stored response is fetched from /v1/responses/:id, not
/api/v1/responses/{response_id}.
Assisted-by: Claude Code:claude-opus-5[1m]
Signed-off-by: Ettore Di Giacinto <mudler@localai.io>
Co-authored-by: Ettore Di Giacinto <mudler@localai.io>
localai.io
The Hugo site served at the root of localai.io. The documentation is a separate
Hugo site in ../docs and is served under /docs/. CI builds both
and uploads them as a single GitHub Pages artifact
(see .github/workflows/gh-pages.yml).
Running locally
From the repository root:
make website # this site only, http://localhost:1313/
make docs # documentation only, http://localhost:1313/docs/
make site # build both, merged into website/public, exactly as CI does
make site-serve # the same merged build, served on http://localhost:8000
make website and make docs run hugo serve, so they pick up edits live but
only cover one site at a time. Use make site-serve when you need the cross
links between the two sites, or the redirects from the pre-split URLs, to work.
make site also runs .github/ci/gen-redirects.sh, which leaves a meta-refresh
page at every URL the documentation used to occupy before it moved under
/docs/. GitHub Pages has no server-side redirects, so those files are the only
thing keeping the old links alive.
Set SITE_BASE_URL to change the base URL the merged build is generated for
(default http://localhost:8000).