Publishing

Preview before publishing

Build and refine an app in a thread, then try its preview. Use Changes to inspect the result and check the behavior before sharing it.

A development preview can depend on a running development server. For a built deployment, the project's build produces the artifact that Continual hosts.

Choose the target and access

Apps belong to a project and branch. Confirm the branch and environment, including its data, before publishing an update.

Choose public or private visibility. Public apps can be opened without signing in; private apps require sign-in. The app's backend still needs to enforce access to its records and actions.

Publish an app

Ask the agent to publish when the app is ready. Continual gives the deployed app a stable URL that you can open and share.

Developers can publish with the CLI. Configure the app package's Continual key, name, and output directory, run its build, then deploy the output.

Dry-run validates the deployment without uploading or publishing. The deploy command uses the selected project and branch; it does not run the app's build for you.

Check deployment history

Open the app to inspect its current deployment. History lists successful deployments and immutable app versions, letting you see which deployment is current.

After publishing, open the app URL and verify the affected workflow. To make another change, return to a thread, review the update, and publish again.

Unpublish an app

Use the app's unpublish action when it should stop being served. Its Continual URL and custom domains stop serving, while versions and deployment history are retained.