How to update a module after XML or manifest changes

Goal: reload manifest.data (views, menus, security XML, demo records) from disk without reinstalling from scratch.

When to use -u

Run an update after you change any of:

• Files listed under manifest.json → data
• manifest.json itself (depends, version, etc.)
• Go model struct fields and sumeru tags (schema sync runs on startup; -u refreshes metadata paths—see below)

Steps

1. Restart is not always required for pure XML if your process reloads on next request, but the supported workflow is via CLI:

```bash shell copy

go run ./cmd/sumeru -- -c sumeru.conf -u engagement_cookbook --stop-after-init

```

1. Or update everything installed:

```bash shell copy

go run ./cmd/sumeru -- -c sumeru.conf -u all --stop-after-init

```

1. Start the server again (or omit --stop-after-init if you want update + HTTP in one process—see sumeru/README.md).

Schema (Go models)

Table alterations run when the server initializes the ORM; changing model fields or tags typically needs a normal server start (or any run that initializes DB). Use -u when you need module metadata and XML reloaded reliably.

See also

• Install a module
• Tooling

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