Waymaker Host

Live and Staging

Learn about Live and Staging in WaymakerOS.

SolutionsLive and Staging

A Solution can have two branches: a Live branch, which is what your customers use, and an optional Staging branch, where you try the whole Solution before it goes Live. Staging is a separate copy of everything in the Solution. Nothing you do in Staging changes Live.

You'll find both in the Solution's settings: open a Solution, choose Settings, and look under Live and Staging on the Overview tab.

What each branch does

  • Live branch. Changes on your Live branch reach your customers through your release mode. See How Your Solution Releases.
  • Staging branch. A push to your Staging branch updates Staging: every app and Agent in the Solution is built from the Staging branch, against Staging's own copies of your databases, sign-in, storage and email.

Staging is optional. Leave the Staging branch empty and there is no Staging: changes on your Live branch go straight to your release mode.

What has a Staging copy

Under Staging copies, each part of the Solution says Has a Staging copy, or why it has none yet. Where something has no Staging copy yet, Staging is not updated at all, and nothing reaches for the Live one instead.

Databases

Each database gets its own Staging copy, made from Live once. Database changes on your Staging branch run on that copy only, before any app that reads it.

Sign-in

Staging has its own sign-ins: invite your team. Your customers' accounts are not copied to Staging, and their passwords don't work there. Staging starts with no users at all.

To let your team in, choose Invite your team next to sign-in. Everyone who is an active member of your organization and has no Staging sign-in yet is invited, and the settings show who was invited. Only members of your organization can be invited to Staging, and only the person who created the app can invite them: if that isn't you, ask them. A Staging sign-in is separate from the same person's Live sign-in. Staging can't send sign-in emails yet, so inviting your team doesn't email anyone, and a Staging "Forgot password" code won't arrive until it can.

Storage

Staging buckets start empty and are always private. Each bucket in the Solution gets its own Staging copy. Files in your Live buckets are not copied, and a Staging bucket is never public and never has a custom domain. Your apps' access to a bucket applies to its Staging copy too.

App email

Staging email only goes to members of your team. Each app that sends email gets its own Staging sending key, made the first time Staging is updated and placed in the app's Staging settings. Nobody is shown it, and it never replaces or ends the app's Live key. Previews never get it: a preview can't send email.

An email sent from Staging goes only to active members of your organization. If any address on an email is not a member, the whole email is refused and nothing is sent. Staging emails go from your app's own sending address, and Staging has its own daily sending limit, separate from Live's. Staging never sets up a sending address, so set up your app's email on Live first: until then, a Staging email is refused.

Apps and Agents

Every app and Agent in the Solution is built from your Staging branch, whatever branch it uses on Live. Ambassadors have no Staging copy yet, so a Solution with an Ambassador that isn't archived cannot be updated in Staging.

Refreshing Staging from Live

Refreshing Staging replaces each database's Staging copy with a fresh copy of Live. A refresh clears Staging's sign-ins again (Staging starts with no users), so invite your team again afterwards. Your Staging buckets and Staging email keys are kept.