Documentation / Deploy
Deploy with installation bindings
Keep workflow logic portable. Use the catalog, runtime groups and approved artifacts from the target installation.
Prepare an application project
shell
rippflow init my-app --lang python
cd my-app
rippflow validate rippflow.yamlThe generated installed-groups.json is a LOCAL example. Replace it with the target installation's catalog before deployment.
Review before publishing
- Select the target installation and its installed runtime groups.
- Build the declared handler artifacts for the target runtime.
- Review the manifest digest, handler bindings and team/project attribution.
- Publish an immutable version, then activate it with the expected active pointer.
Inspect versions first
shell
rippflow workflows list --json
rippflow versions WORKFLOW_NAME --jsonActivation and rollback are reviewed mutations. Use the target installation's contract and exact version/binding preconditions.
Verified sources
Checked 2026-11-05.
- Application project and catalog generation 7f5ea32 · main
- Deployment review and active-version operations 7f5ea32 · main
- Controller behavior and release boundaries f6c7970 · main
