Files
LocalAI/website
Ettore Di Giacinto 4a5c5e51b7 website: say plainly that engines are swappable behind the same API
The runtime section described the small core and on-demand backends but
never stated the simple fact readers look for: one model can run on
llama.cpp while the next loads on vLLM, SGLang or MLX, behind the same
endpoint, and switching is one line in the model's config.

Signed-off-by: Ettore Di Giacinto <mudler@localai.io>
Assisted-by: Claude Code:claude-fable-5
2026-08-05 07:33:08 +00:00
..

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).