DEV Community

Cover image for Seven steps of an Orbi Cloud setup, on video
Lawrence Liu
Lawrence Liu

Posted on Originally published at orbi.build

Seven steps of an Orbi Cloud setup, on video

#ai #tutorial #devops #github

The full setup is now on video: Orbi Cloud: from zero to a tagged release in seven steps. It is 83 seconds long, in English, and divided into chapters so you can skip to the step where you are stuck.

Watch the complete seven-step Orbi Cloud setup.

Seven key screens from the seven-step flow

Orbi Cloud sign-in screen
Step 1: Orbi Cloud sign-in screen.

GitHub App installation screen
Step 2: GitHub App installation screen.

Repository connection form
Step 3: Repository connection form.

Environment provisioning status
Step 4: Environment provisioning status.

First Issue status screen
Step 5: First Issue status screen.

Release form with version field
Step 6: Release form with version field.

Managed Cloud subscription screen
Step 7: Managed Cloud subscription screen.

The seven steps are the current Cloud onboarding path:

  1. Sign in with your GitHub identity.
  2. Install the Orbi GitHub App on your account.
  3. Connect a repository: the repo and the base branch Orbi works from.
  4. Provision the environment. About a minute.
  5. Your first Issue. Label it ai-ready, and Orbi writes the code and opens a pull request.
  6. Cut a release. Type the version; Orbi bumps it, tags it and publishes the GitHub Release.
  7. Subscribe. The first 3 deliveries are free; paid plans are Solo at US$29/month with 100M tokens, or Pro at US$79/month with 300M tokens. When the allowance runs out, only new deliveries pause: your data stays intact, and you can cancel at any time.

The seventh step is the one that starts paid delivery

Steps one through six are setup and delivery: you are handing Orbi the things it cannot infer: an identity, an installation, a repository, a runtime, an Issue, and a release. Step seven is where you opt into the Managed Cloud plan after the 3 free deliveries.

The release step still requires your decision: you decide the version, Orbi never increments it for you. The runner will bump the version file, create the tag and publish the Release. It will not choose the number. A version is a claim about what changed and who should care. That is a product decision, and reading it off a counter would be pretending otherwise. The release scope comes from the Milestone carrying that exact title; without one, the release stops at scope derivation and tells you why.

Step five is one label, and you can add it without leaving the terminal:

gh issue edit <number> --add-label ai-ready
Enter fullscreen mode Exit fullscreen mode

What you are actually looking at

Every screen in the video is the product rendering, not a mockup: the sign-in card, the connect form with its repository and base-branch fields, the progress bar counting the step you are on, the connected-repository table with its provisioning status, the release form with the version box, and the subscription step. The GitHub App page is the real one at github.com/apps/orbi-build.

If you want to read instead of watch, the same path is in the docs: docs.orbi.build. If you want to run the whole thing on your own machine instead of ours, that is the same product, free to self-host.

Start here: orbi.build/cloud.

Related

Read the Google Jules comparison and Cloud.

Top comments (0)