master now bounds a README Summary at 100 words; the boot group, the plugin manager, and its host face say the same in fewer. The zh config catalog gains the paragraph break the merge dropped.
2.2 KiB
2.2 KiB
description, kind
| description | kind |
|---|---|
| The boot package group: how dsh app bins start — environment loading, profile and patch layers, clear startup failures, and app-owned command lines. | package-group |
boot/ — shared app-bin boot glue
English | 中文
Summary
The boot group provides what every dsh app bin needs to start and to manage what it starts: app-boot turns a cordis.yml plus your environment and patch layers into a running app with clear failure messages, cmdline lets the app own its command-line flags and --help, and plugin-manager installs, enables, and edits a profile's plugins for the dsh plugin command and the Web host alike. All three are libraries imported by apps/cli, host packages, and test-only Loader fixtures, never plugins a composition loads; each package README owns its contract.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
app-boot |
Boots a dsh app from a cordis.yml: loads .env, applies profile and patch layers, and reports startup failures clearly |
(library for the bins) |
cmdline |
Lets the app own its flags, --help, and exit code; passes everything after the launcher's flags through verbatim |
cmdlineArgs, appExit |
plugin-manager |
Installs and probes packages without booting, and enables, disables, retries, and edits user-layer rows over the booted profile; the dsh plugin command and the Web host's plugins Remote share it |
(library for the bins and the host) |
Related documentation
- dsh app — the
dshbin that consumes these helpers for its boot sequence. - Profile bundles — installable patch layers that
dsh --profilecompositions mount. - dsh-home-paths — the harness-home resolver both packages build on.
- dsh-cmdline — how an app owns its flag family instead of the launcher.
Dev Note
None.