Skip to main content
A Nuxt application runs on Sevalla as an application: Nixpacks runs nuxt build from your Git repository, which builds a Node.js server with Nitro, and the web process starts that server on the port that Sevalla sets in the PORT environment variable. A site whose pages can all be prerendered can instead be generated and published as a static site.

​
Before you begin

  • A Sevalla company with a payment method, and a GitHub, GitLab or Bitbucket account for the repository. See Git providers.
  • Node.js 24 or later on your computer.

​
Create the project

Create a project and answer the prompts (package manager, Git repository, modules):
The project comes with a .gitignore and the build, dev, generate and preview scripts, but no start script.

​
Prepare the project for Sevalla

Add the start script and pin the Node.js version:
Nitro’s Node.js server, the default output of nuxt build, takes its port from NITRO_PORT or, when that isn’t set, from PORT, which Sevalla sets to the web process’s port (8080 by default), and listens on all network interfaces. No change to nuxt.config.ts is needed. Nixpacks 1.41 installs Node.js 24.10.0, and Nuxt 4.6 lists 24.15.0 or later in its engines field, so the build log shows warnings about an unsupported Node.js version. The warning doesn’t stop the build. To build with the newest Node.js 24 release instead, switch the build strategy to Railpack (Beta). Run npm run build && npm start and open http://localhost:3000 to check the production build locally. Then commit everything and push it to your Git provider:

​
Deploy to Sevalla

1

Create the application

In the sidebar, click Applications, then click Create > Application. Under Source, click Private repository, then choose the Git provider, the Repository and the Branch. Under Location, choose a Data center. Keep the Size at H1 or choose a larger one, then click Create application. The application opens on its Overview tab with the status Not deployed yet: creating an application doesn’t deploy it.
2

Deploy

Click the Overview tab, then click Deploy now under Recent deployments. Check the Branch and click Deploy.
3

Turn on auto-deploy

To deploy every push to the branch automatically, click the Settings tab, then click Update auto-deploy in the Auto-deploy section. Turn on Auto-deploy and click Update auto-deploy. See Deployments.

​
Verify the deployment

  1. On the Deployments tab, wait for the deployment’s status to change to Deployed. The application’s status next to its name changes to Running.
  2. Click the domain under the application’s name, for example storefront-x7k2m.sevalla.app. The Nuxt welcome page opens.
The application header with its name, Running status, repository, branch and the domain that opens the applicationThe application header with its name, Running status, repository, branch and the domain that opens the application
If the deployment fails, open it on the Deployments tab and read its build log, then see Troubleshoot builds and deployments. If the deployment fails while the instances start, check that package.json has the start script.

​
Deploy changes

With Auto-deploy on, every push to the branch starts a deployment; otherwise, click Deploy now for each change. Each deployment builds the image, then replaces the web process’s instances. See Deployments.

​
Use environment variables

Add configuration on the application’s Environment variables tab. Nuxt overrides each key in runtimeConfig with a variable named NUXT_ plus the key in uppercase snake case at runtime, so runtimeConfig.apiSecret reads NUXT_API_SECRET. Variables apply at the next deployment. See Environment variables.

​
Deploy a generated static site

When every page can be prerendered, nuxt generate writes the site to .output/public, and Sevalla publishes it as a static site, free up to 100 GB of bandwidth a month. Server routes and on-demand rendering don’t run on a static site. The project needs no changes: the generate script is already in package.json.
1

Choose the repository

In the sidebar, click Static sites, then click Create static site. Under Source, click Private repository, then choose the Git provider, the Repository and the Branch.
2

Check the build settings

Under Build settings, Sevalla shows Framework detected: Nuxt.js and fills in the values. Check them:
3

Create the static site

Enter a Name under Details, then click Create static site. Sevalla starts the first deployment right away, and deploys every push to the branch while Auto-deploy is on.
When the deployment’s status changes to Deployed, click Visit site on the static site’s Overview tab. If the deployment fails, see Troubleshoot static sites. See Build settings for every field.

​
Add a custom domain

To serve the application from your own domain, such as shop.example.com, add the domain on the application’s Domains tab and create the DNS records that Sevalla shows. Custom domains need a web process larger than H1, so scale the web process first. Static sites have a Domains tab too. See Custom domains.

​
Connect a database

Create a database in the same location as the application, then connect the application to it with Add environment variables to the application turned on. Sevalla adds DB_URL, DB_HOST, DB_PORT, DB_DATABASE, DB_USERNAME and DB_PASSWORD to the application (what each one holds), and they apply at the next deployment. Read them in server routes with process.env.DB_URL.