Skip to main content
A static site’s Settings tab holds every setting of the site, in five groups: General, Deploy, Build, Redirects and Danger zone. This page lists each setting and links to the page that explains it in depth. Build and deploy changes apply from the next deployment.
Changing a setting needs permission to update the static site; without it, the buttons are disabled and say why. Deleting needs permission to delete it, and the Danger zone is hidden without it. See Users and roles.
While a production deployment runs, you can’t update the display name, source, automatic deployments, pull request previews or build strategy, or delete the site. The change fails with Deployment is in progress, cannot delete site. Wait for the deployment to finish, or cancel it.

General

Details

To rename the site, click Update display name, enter the new Display name, then click Update display name. The name in URLs and the domain stay the same.
The General group of a static site's Settings tab: Details with the display name, name and ID, and the Update display name buttonThe General group of a static site's Settings tab: Details with the display name, name and ID, and the Update display name button

Deploy

Which sections a site has depends on its source:

Source

1

Open the source settings

Under Source, click Update source.
2

Choose the new source

Click Private repository or Public repository. For a private repository, choose the Git provider and the Repository. For a public one, enter the Repository URL.
3

Save it

Click Update source.
The next deployment builds from the new repository. The default branch doesn’t change, so check that the new repository has it: update it in Auto-deploy, or deploy another branch by hand. Changing the source type needs a valid payment method on the company. If Sevalla can’t read the repository, the update fails with Repository not found for URL "<url>".

Auto-deploy

Shows whether every push to the default branch deploys (Status Enabled or Disabled) and the Default branch. Click Update auto-deploy to turn it on or off and to change the default branch. See Deploy automatically on push.

Git Large File Storage (LFS)

Shows whether builds download Git LFS objects (Enabled or Disabled, enabled for new sites). Click Disable Git LFS or Enable Git LFS, then confirm. See Git LFS.

Deploy paths

Shows which pushes start an automatic deployment (Every change deploys, Only changes in these paths deploy or Changes in these paths don’t deploy) and lists the patterns. Click Update deploy paths to change them. See Choose which changes deploy.

Pull request previews

Shows whether pushes to other branches build previews (Enabled or Disabled, disabled for new sites). Click Enable previews or Disable previews, then confirm. See Pull request previews.
The Deploy group of a static site's Settings tab: Source, Auto-deploy enabled on main, Git LFS disabled, Deploy paths with every change deploying, and Pull request previews disabledThe Deploy group of a static site's Settings tab: Source, Auto-deploy enabled on main, Git LFS disabled, Deploy paths with every change deploying, and Pull request previews disabled

Build

Build strategy

Shows the Build command, Node version, Root directory, Publish directory, Index file and Error file. Click Update build strategy to change them, then deploy the site. See Build settings for every field and its default.

Redirects

Pretty URLs

Shows whether Sevalla adds a trailing slash to page URLs (Enabled or Disabled, disabled for new sites). Click Enable pretty URLs or Disable pretty URLs, then confirm. The change applies without a deployment; purge the cache afterwards. See Pretty URLs.

Danger zone

Delete a static site

Deleting a static site deletes its deployments, its files, its environment variables and its domains, including the sevalla.page domain. You can’t undo this or recover the site.
1

Start the deletion

Under Danger zone, click Delete static site.
2

Type the site's name

In the dialog, type the site’s name as shown, for example acme-shop-k3x9p.
3

Delete it

Click Delete static site.
The dashboard goes back to the Static sites list, where the site shows Deleting until it’s gone. Remove the DNS records of its custom domains at your DNS provider: Sevalla doesn’t change them. Browsers that cached the site’s files can show them for a while longer.
The Danger zone of a static site's Settings tab with the Delete static site buttonThe Danger zone of a static site's Settings tab with the Delete static site button

API and CLI