Expand description
Forjar — Rust-native Infrastructure as Code.
Bare-metal first. BLAKE3 state hashing. Provenance tracing. Faster, more provable, more sovereign than Terraform, Pulumi, or Ansible.
§Using forjar as a library
Start at api. That module is the supported surface and the only part
of this crate covered by semver.
Everything else — the seven modules below and roughly 1,844 pub items
beneath them — is reachable and documented, but it is implementation. It may
be renamed, moved or removed in a patch release. Depending on it is fine if
you know that; pin an exact version when you do (GH-240).
Modules§
- api
- The supported, semver-covered library API. See the module docs. The supported library API.
- cli
- CLI dispatch, subcommands, and output formatting.
- copia
- FJ-242 (rolling): copia rolling delta sync for large-file provisioning.
- core
- Core infrastructure logic — types, parsing, resolution, planning, execution.
- mcp
- FJ-063: MCP integration via pforge.
- resources
- Resource handlers — generate purified shell for each resource type.
- transport
- FJ-010/011/021/230: Transport abstraction — local, SSH, container, and pepita execution.
- tripwire
- Tripwire — provenance tracing, BLAKE3 hashing, drift detection, syscall tracing.
- verb
- The forjar Unified Verb Surface (FVS).