Ctrlk
Home
linkedinyoutube
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Training Examples

This section explains the training examples deployed with standard Rierino installations, which can be used as starter templates.

Training examples ship with a standard Core installation. Use them as starter templates. Use them to validate your setup end-to-end.

Most examples are intentionally small. They show one idea at a time. You can copy the pattern into real services.

This section covers Core examples. Core is available to all users.

For Core vs Core+ feature comparison, see Rierino Packages.

What’s included

You get three sets of assets. They map to the three main “build surfaces” in Rierino.

Cover
Title

API Flow Examples

Target
API Flow Examples
Cover
Title

Microservice Examples

Target
Microservice Examples
Cover
Title

UI Example

Target
UI Example

Recommended path (30–60 minutes)

Do these in order. Each step builds on the previous one.

  1. Build a minimal API flow: Exercise: Hello World API

  2. Expose a new CRUD collection: Exercise: Test State

  3. Add a UI on top of that CRUD endpoint: Exercise: Test UI

If you already have a working environment, start with Hello World API. It is the fastest routing smoke test.

Where to find the training assets

Devops → Sagas (API Flows)

Open the Devops app, then Saga.

Training sagas are grouped under the training domain. Start with:

  • /train_ping (echo / smoke test)

  • /train_hello (transform → response)

  • /train_get and /train_set (read/write against state)

Full list and screenshots: API Flow Examples.

Devops → Runners + Deployments (Microservices)

Open the Devops app, then Runner and Deployment.

The training deployment typically includes:

  • train_rpc: executes sagas as APIs

  • train_crud: generic CRUD microservice

  • train_cdc: listens to DB changes and triggers a saga

Details and videos: Microservice Examples.

Design → UIs + Source + Apps (Admin UI)

Open the Design app.

The built-in training UI shows how to wire a lister + editor to a CRUD backend:

  • UI: screen layout (tabs, widgets, lister columns)

  • Source: API mapping (typically train_crud/dummy)

  • App: menu packaging (a minimal training app)

Walkthrough: UI Example.

API endpoints cheat sheet

Use these patterns when testing from Postman or curl. Replace YOUR_ADMIN_API_DOMAIN with your gateway domain.

Sagas are case-sensitive. Runner configs may reload on a short interval (often ~10–30 seconds).

Next step

Once these patterns feel familiar, build something end-to-end with the larger guided exercise:

PreviousQuick Start FAQ
NextAPI Flow Examples

Last updated