rn-forge-tooling¶
rn-forge-tooling is the lifecycle and install layer of the developer-tooling
stack: for command-line tools that install themselves and manage their own
versions. File generation, local state and templates live in rn-forge-commons.
It provides:
- the tool lifecycle:
$RNF_HOMElayout, release fetching and verification, and transactional install/upgrade/uninstall/cleanup/status/doctor verbs build_tool_app, which builds anrn-forge-cliapplication from a[cli]table and adds the lifecycle verbs declared in a[lifecycle]table
Where rn-forge-commons is runtime-neutral — safe in a web server, a worker or
a container — and rn-forge-cli is the command-line shape every application
wants, this package is deliberately workstation-shaped: it assumes a developer's
filesystem and a tool that owns files in it. A repository that only needs a
command line takes rn-forge-cli and stops there. A package that ships into a
deployed runtime must not depend on this one outside a codegen extra;
task lint enforces that.
Install¶
dependencies = ["rn-forge-tooling>=0.3,<0.4"]
The testing extra installs assertpy and pytest. Minimum example:
Tool lifecycle.
Errors:
What install guarantees.
Use the guides for common workflows and the API reference for module details.