Three modules

Why the three replace-linked modules exist, and why you run from the workspace.

Why three modules

Go modules map to the three git repos: sumeru, sumeru_addons, and sumeru_custom_addons. The workspace replaces the first two so go run . links local checkouts.

1sumeru_custom_addons  --replace + generate-->  sumeru2         |                                    |3         +--addons_path-----------------------+--> HTTP server4         |5         +--also loads sumeru_addons

Run from the workspace

Recommended entry is always sumeru_custom_addons: it owns sumeru.conf, blank-imports, and your addons. Core-only make run is for kernel development.

Compile and run

$cd sumeru_custom_addons$make replace-sumeru$make replace-sumeru-addons$make generate$make run

What not to do

• Do not vendor a private fork of core per customer if pull-only updates would suffice.
• Do not omit replace and expect sibling folders to resolve magically.

Next step

See how tables are built in ORM.

Sumeru is pre-alpha (no tagged release, no upgrades). Part of Project Meru.