Development
Building the Docker image
Section titled “Building the Docker image”The multi-stage Dockerfile builds the frontend (Node 24) and backend (.NET 10) into an aspnet:10.0 runtime image that serves the SPA from wwwroot/.
docker build -f distribution/docker/Dockerfile -t maki:local .
docker run -d --name maki \ -p 8990:8990 \ -v "$PWD/maki-config:/config" \ -v "/path/to/manga-library:/library" \ maki:local
# Multi-arch push with Buildxdocker buildx build -f distribution/docker/Dockerfile --platform linux/amd64,linux/arm64 -t ghcr.io/<you>/maki:latest --push .- The build context must be the repo root. Both stages copy
locales/in (the API embedsserver.po, Vite bundlesclient.po), and the build fails if a language is missing from either stage. distribution/docker/entrypoint.shfixes ownership of/configand drops toPUID/PGIDviagosu.- State lives in the
/configvolume. The library is a separate mount you can share with Kavita. - CI and the
distribution/build-*.ps1scripts build this same file.
Running from source
Section titled “Running from source”# Backend (http://localhost:8990, Swagger at /swagger in the Development environment only)dotnet run --project src/Maki.Api
# Frontend dev server (http://localhost:5173, proxies /api and /signalr)npm --prefix frontend run dev
# Testsdotnet test
# Release publishdotnet publish src/Maki.Api -c ReleaseState (database, logs, covers, caches, MangaBaka dump, embeddings, recommendation data) lives in MAKI_CONFIG_DIR. The fallback order is in Environment variables and the contents in Ports, paths and files on disk. For development, point it at a throwaway directory:
MAKI_CONFIG_DIR="$PWD/.devconfig" dotnet run --project src/Maki.ApiEF Core migrations apply automatically on startup. Before changing code, see the Architecture tour for what goes where.