Main
A pragmatic way to evaluate RocketRide:
- Install the IDE extension and create a tiny pipeline with a single source node (chat/webhook/dropper).
- Add one transform node (chunking, OCR, or NER) so you can see a meaningful trace.
- Run from the canvas and inspect tracing: confirm you can answer “what called what” and “where did tokens go”.
- When it’s stable, move the runtime to Docker/on-prem as the README shows, and treat the
.pipefile as a deployable artifact.
The goal isn’t “more nodes”; it’s repeatable pipelines with observable cost and latency.
FAQ
Q: Do I need Docker to start? A: Not necessarily. The README describes a local (IDE-pulled) option and also provides Docker deployment steps.
Q: What is a pipeline file?
A: The README says pipelines are recognized as *.pipe JSON objects rendered by the IDE canvas.
Q: Does it have observability? A: Yes. The README has an Observability section describing tracing and analytics for running pipelines.