Preview, Beta and Live

Coming in the first release. This page describes behaviour being built for the first Gliss release. Details may change before it ships.

People believe that whatever they are looking at is the app. So every Gliss app runs in three separate stages, each with its own database, secrets and address.

	Preview	Beta	Live
Who sees it	You, and people you invite	Invited testers	The audience in `gliss.yaml`
What runs	Your branch, with changes in seconds	The app as merged, built by CI	Exactly the images that passed Beta
Secrets	Mock mode by default	Requested, or mock	All must be set
When idle	Sleeps after 30 minutes; deleted after 7 days	Sleeps after 30 minutes	Always on
Moves on with	Share to beta	Publish

Your IT team’s catalog can change the idle times.

Preview

Your private workspace. With a runtime that supports it (Python and Vite in the first release), a saved change shows in about 5 to 10 seconds, without a full rebuild. A sleeping Preview wakes on the next visit. The app’s GLISS_STAGE variable tells it which stage it is in. Show a visible badge on Preview and Beta, for example “Preview: only you can see this”.

Beta

Built from the main branch, for real, by your company’s CI. Every merge updates it. Share the link with testers.

Live

Live never rebuilds. Publish promotes the exact images that ran in Beta. See Share and publish for what Publish checks.

Per-stage settings

stages:
  preview: { config: { LOG_LEVEL: debug } }
  beta:    { secrets: { SALESFORCE_TOKEN: request } }
  live:    { config: { LOG_LEVEL: warning } }

Every stage may override config. Preview and Beta may also choose mock or request for each secret. Live may not: every secret must be set before Publish.

Get started

Build apps

Administer

Engineers

Troubleshooting

Preview, Beta and Live

Preview

Beta

Live

Per-stage settings

​Preview

​Beta

​Live

​Per-stage settings

Preview

Beta

Live

Per-stage settings