deploy
| plugin-fleet — Served by | plugin-fleet |
| plugin-fleet — Placement | compiled-in (in-process) |
| plugin-fleet — Version | 2026.193.1200 |
| plugin-fleet — Served by | plugin-fleet |
| plugin-fleet — Placement | compiled-in (in-process) |
| plugin-fleet — Version | 2026.193.1200 |
deploy is a command word served by 2 plugin candies — plugin-fleet and plugin-fleet — at different points in the command tree. Both are real invocations; charly --help prints which is which.
About plugin-fleet, which serves it
Section titled “About plugin-fleet, which serves it”The charly deploy … deployment CLI, externalized into a COMPILED-IN
command:deploy plugin (F8) mirroring candy/plugin-vm. charly deploy add
/ del / show / export / import / reset / path / status /
from-box dispatch IN-PROC via Invoke(OpRun) (runDeployCommand →
kong-parse the DeployCmd tree), so the handlers run in charly’s OWN process
and inherit charly’s real stdio/TTY natively. Each leaf FORWARDS its parsed
flags to the host over four generic host-build seams — HostBuild deploy-add /
deploy-del / deploy-from-box (the deploy dispatch) and deploy-config (the
show/export/import/reset/status config-management ops) — where the host runs
the existing deploy orchestration VERBATIM: the config loader + deploy ledger,
the InstallPlan compiler, and the deploy-dispatch kernel (ResolveTarget →
the plugin-side deploy dispatcher over the executor reverse channel) all STAY
core. path
resolves plugin-side via kit.DefaultDeployConfigPath (no seam). command:deploy
is COMPILED-IN; its grammar is prescanned into the CLI.
About plugin-fleet, which serves it
Section titled “About plugin-fleet, which serves it”The charly deploy … deployment CLI, externalized into a COMPILED-IN
command:deploy plugin (F8) mirroring candy/plugin-vm. charly deploy add
/ del / show / export / import / reset / path / status /
from-box dispatch IN-PROC via Invoke(OpRun) (runDeployCommand →
kong-parse the DeployCmd tree), so the handlers run in charly’s OWN process
and inherit charly’s real stdio/TTY natively. Each leaf FORWARDS its parsed
flags to the host over four generic host-build seams — HostBuild deploy-add /
deploy-del / deploy-from-box (the deploy dispatch) and deploy-config (the
show/export/import/reset/status config-management ops) — where the host runs
the existing deploy orchestration VERBATIM: the config loader + deploy ledger,
the InstallPlan compiler, and the deploy-dispatch kernel (ResolveTarget →
the plugin-side deploy dispatcher over the executor reverse channel) all STAY
core. path
resolves plugin-side via kit.DefaultDeployConfigPath (no seam). command:deploy
is COMPILED-IN; its grammar is prescanned into the CLI.
charly --help prints the command tree, including where each deploy is invoked and under which parent.