Skip to main content
An application’s Settings tab holds everything about how the application is named, where its code comes from, how it deploys and builds, and the actions that stop or remove it. It’s grouped into General, Deploy, Build and Danger zone. Settings that change the build or the runtime take effect with the next deployment; the dashboard lists them as undeployed changes until you deploy. To open it, click Applications in the sidebar, click the application, then click the Settings tab.
Changing a setting needs permission to update the application. Suspending, activating and deleting need permission to delete it: company owners, company admins, company developers, project admins and project developers have it; app administrators don’t. See Users and roles.

General

The General group of an application's settings with Details, Hibernation and Maintenance modeThe General group of an application's settings with Details, Hibernation and Maintenance mode

Details

To rename the application, click Update display name, enter the new Display name, and click Update display name. The Name, the hostname and the URLs don’t change.

Hibernation

Hibernation scales the application to zero when it receives no HTTP requests for the time you set. The application wakes on the next HTTP request, usually within 90 seconds; Sevalla holds that first request for up to about 3 minutes while it starts. The section shows its Status and, when it’s on, Hibernate after with the idle time. To change them, click Update hibernation. Hibernation can’t be on while any process uses horizontal autoscaling. See Hibernation for how it works and what it saves.

Maintenance mode

Maintenance mode serves a maintenance page with status 503 on every domain of the application while it keeps running. The section shows its Status and, when it’s on with a custom page, the Maintenance page URL. See Maintenance mode.

Deploy

The Deploy group of an application's settings with Source, Auto-deploy, Git LFS, Deploy hook and Deploy pathsThe Deploy group of an application's settings with Source, Auto-deploy, Git LFS, Deploy hook and Deploy paths
Which sections you see depends on the source:

Source

To change where the code comes from, click Update source. You can switch between a private repository, a public repository and a Docker image, pick another repository or provider, or change the image and its registry credential. Click Update source to save. The new source is used from the next deployment; the branch and the build settings don’t change. To change the branch, use Auto-deploy (private repositories) or pick it when you deploy by hand.

Auto-deploy

Private repositories only. Status shows whether Sevalla deploys on every push to the Default branch. To change either, click Update auto-deploy, turn Auto-deploy on or off, choose the Branch, and click Update auto-deploy. The default branch is also the branch that manual deployments and deploy hooks use unless you pick another. See Deploy automatically on push.

Git LFS

The Git Large File Storage (LFS) section controls whether Sevalla downloads files tracked with Git LFS when it clones the repository for a build. It’s on by default. When it’s off, LFS-tracked files are checked out as small text pointers instead of their content, which is faster when the build doesn’t need them. To change it, click Disable Git LFS (or Enable Git LFS) and confirm. The change applies from the next deployment. Git sources only.

Deploy hook

A deploy hook is a secret URL that starts a deployment when it receives a POST request. Click Enable deploy hook to get one; the section then shows the Deploy hook URL, with Regenerate to replace it and Disable deploy hook to turn it off. See Deploy with a deploy hook.

Deploy paths

Private repositories only. Deploy paths decide which pushes start an automatic deployment, by the files they change. Status reads Every change deploys, Only changes in these paths deploy or Changes in these paths don’t deploy, followed by the list of patterns. To change them, click Update deploy paths. See Deploy only when some files change.

Build

Git sources only. The Build strategy section shows how Sevalla builds the application: To change them, click Update build strategy. Every field is explained in Builds; each builder has its own page.

Danger zone

The Danger zone of an application's settings with Suspend app and Delete appThe Danger zone of an application's settings with Suspend app and Delete app

Suspend an application

Suspending stops the application without deleting anything: every process scales to zero instances, the application is unavailable, and every live connection closes. Its settings, environment variables, disks, domains and deployment history stay. You aren’t billed for its processes while it’s suspended.
1

Start the suspension

In the Danger zone, click Suspend app.
2

Confirm

In the Suspend app dialog, click Suspend app.
The application’s status changes to Suspended and the Danger zone shows Activate app instead.

Activate an application

1

Start the activation

In the Danger zone, click Activate app.
2

Confirm

In the Activate app dialog, click Activate app.
Every process scales back to its instance count and the application serves traffic again. The status leaves Suspended.

Delete an application

Deleting an application deletes all of its data: processes, deployments and their images, environment variables, disks and their files, domains, TCP proxies and its internal connections to databases and other applications. You can’t undo this, and the data can’t be recovered.
1

Start the deletion

In the Danger zone, click Delete app.
2

Confirm with the name

In the Delete app dialog, type the application’s Name (for example storefront-x7k2m, not the display name), then click Delete app.
Sevalla cancels any deployment that’s running or queued, then deletes the application. You land on the Applications list, where the application shows as Deleting until it’s gone. If it shows Deletion failed, contact support.

API and CLI