Installation
Create a database, configure the workspace, and point it at the core and standard addon modules.
Pre-alpha. Sumeru has no tagged release and no upgrade path. Fine for local eval and addon work. Do not run production on it.
Requirements
- Go 1.26+
- Node.js (npm — builds SWC workspace UI; bundles are gitignored)
- PostgreSQL
- Checkouts of
sumeru,sumeru_addonsandsumeru_custom_addonsas sibling directories (typical layout)
make setup wires go.mod replaces, regenerates imports, and builds client assets when missing. Docker, a message broker, and external cache are not required.
Create the database
psql -U postgres -c "CREATE DATABASE sumeru;"
Workspace config
All commands below run from your workspace module, sumeru_custom_addons.
cd sumeru_custom_addonscp sumeru.conf.example sumeru.confedit db_host / db_user / db_password / db_name / http_port (default 8080)
Paths inside the INI resolve against the file itself, not your shell. The addons_path key decides which addons exist at all. Default listen port is 8080. Details: Configuration.
Bootstrap the workspace
make setupgo.mod replaces, imports, SWC + login JS bundlesmake runregenerate imports; rebuild assets when missing or stale
make setup runs replace-sumeru, replace-sumeru-addons, make generate (rewrites addonimports/zimports.go), and make assets (delegates to ../sumeru for SWC bundles). Run make generate again whenever you add an addon folder.
Verify the toolchain
go versionnode --versionnpm --versionpsql -U postgres -c "SELECT version();"
Next step
Continue with Configuration if you need every key explained, or jump to First boot to run the setup wizard.
What not to do
- Do not run server commands from the core or addons module; use the workspace.
- Do not skip
make generateafter adding an addon folder. - Do not assume Docker is required; it is not.