export
Package a complete static catalogue you can deploy anywhere.
Usage
npx mokly export --out .context/mokly-siteOptions
| Option | Meaning |
|---|---|
--out <path> |
Config-relative export directory; required |
--config <path> |
Use an explicit mokly.config file |
--base <ref> |
Git base ref used to find the branch point |
--debug-timings |
Report phase timings and catalogue counts on standard error |
What it produces
Export builds first, then packages the catalogue: every screen and page, the real id aliases, the assets and the Git comparisons. The result is a directory of static files. Export never uploads anything.
Deploy the directory’s contents at the root of an HTTP(S) origin. Hosting requirements are on the Catalogue page for export and hosting.
The destination
--out resolves beside the loaded config rather than your working directory,
and an absolute path must stay inside the repository root. Choose a directory
that is missing or empty and outside your source, generated, dependency and
comparison roots, and keep unrelated files out of it.
A re-export replaces only the output it owns, and restores the previous site if installation fails and recovery is safe. If something else recreates the destination while an export is running, both it and the captured backup are kept for you to recover by hand.
History
--base overrides review.base, which defaults to origin/main. The branch
point must exist in the checkout together with the authored assets and either
the committed generated output or the tooling a derived baseline rebuild
needs. In CI, check out the full history.