Going live

A new app ends its setup live. What still needs you, and how to rotate a key.

Your app goes live on its own. When the setup agent finishes, Rendel publishes the Appearance and Experience drafts and turns the live key on, if four checks pass.

The Go live checks

CheckPasses whenIf not
The SDK has called inA build has started with your key at least onceRun the app once with the test key
The app sent its manifestThe SDK sent its actions and screens, which it does at initRun a build that calls Rendel.init
Knowledge is indexedAt least one knowledge source is ReadyAdd a source under Knowledge
The last smoke test passedAt least 80% of its answers were grounded or backed by an actionRun smoke test on Overview, fix what it shows

Until then the live key is refused with 403 app_not_live: the SDK hides the launcher and logs one warning, and the test key keeps working. If a check was still open when the agent finished, Overview names it and Go live turns the key on once it passes.

What still needs you

  • Ship a release build. Merge the rendel/setup branch; the agent wired the live key into release builds, or listed the swap in its to-dos.
  • Keys the agent could not enter. An endpoint that needs a shared API key is saved switched off: Actions → Add key.
  • Websites: list your production domains under Settings → Security → Allowed domains.
  • Every week: open Improve. Unanswered questions and failing actions are your backlog.

After go-live a setup file can no longer change the app (409 app_live). Changes from your code go through Sync with code, where a person reviews them.

Rotating a key

Rotating issues the new key at once and keeps the old one working for seven days on live, one day on test. Ship the new key inside that window.