App

In Reflex Cloud an "app" (or "application" or "website") refers to a web application built using the Reflex framework, which can be deployed and managed within the Cloud platform.

You can deploy an app using the reflex deploy command.

There are many actions you can take in the Cloud UI to manage your app. Below are some of the most common actions you may want to take.

To stop an app follow the arrow in the image below and press on the Stop app button. Pausing an app will stop it from running and will not be accessible to users until you resume it. In addition, this will stop you being billed for your app.

To delete an app click on the Settings tab in the Cloud UI on the app page.

Then click on the Danger tab as shown below.

Here there is a Delete app button. Pressing this button will delete the app and all of its data. This action is irreversible.

Clicking on the Settings tab in the Cloud UI on the app page also allows a user to change the app name, change the app description and check the app id.

The other app settings also allows users to edit and add secrets (environment variables) to the app. For more information on secrets, see the Secrets (Environment Variables) page.

Every reflex deploy creates a new deployment. List an app's deployment history — each deployment's status, Python/Reflex versions, VM type, optional description, and whether it can be rolled back to — with:

If you omit APP_ID, the app is resolved from the appid in your cloud.yml/pyproject.toml, or you can pass --app-name. Add --json for machine-readable output.

You can attach a short changelog note to a deployment so your history is easy to scan (for example, "bump pricing page copy"). Set it at deploy time:

You can also set or replace the note on an existing deployment. Find the deployment id with reflex cloud apps history, then:

Pass --description "" to clear the note. Descriptions show up in reflex cloud apps history and in the Cloud dashboard.

If a deploy introduces a regression, you can roll back to any previous deployment that still has a built image. A rollback redeploys that deployment's existing image — no rebuild from source — and makes it current again, demoting the currently running deployment to history.

Use reflex cloud apps history to find rollback-eligible deployments: their can rollback value is True. A deployment can only be rolled back to on the provider whose registry holds its image, so after switching an app's provider the deployments built on the previous provider are no longer offered as rollback targets.