Sign up free
Precision-built server with three removable modules and evenly spaced ventilation holes
Managed-hosting comfort on servers you own.See pricing
A machined control panel: CONTROL
Search every capability.All features
A globe beside a compact provider server
Compare providers, plans and prices.Compare providers
Source and target modules joined by a continuous connector
Cloudflare, Git, storage, AI agents and alerts.All integrations

Keep data between releases

Updated October 7, 2026 · 2 min read

Make sure uploads, SQLite databases and other files your Node.js app writes survive every deploy and rollback, by keeping their folders in shared storage.

On this page
  1. Why this matters
  2. Step 1: Open the persistent storage settings
  3. Step 2: Add the folders
  4. Step 3: Save and redeploy
  5. When Nuvlo finds unknown folders

Before you start

  • A Node.js app that deploys with atomic releases (the default for new apps).
  • Permission to manage sites in your Nuvlo account.

Why this matters

Every deploy builds a fresh release from your repository. Files the running app wrote into its own folder, such as user uploads or an SQLite file, would be left behind in the old release.

A persistent path is a folder that lives in shared storage instead. Every release uses the same copy, so its content survives deploys and rollbacks.

PHP sites don't need this for the usual cases: their .env and, for Laravel, the storage folder are kept between releases automatically.

Step 1 Open the persistent storage settings

Open the app from Sites, go to Settings, General, and scroll to Persistent storage at the bottom of the Build and deployment card.

Step 2 Add the folders

Click Add path and enter the folder relative to the app's root directory, for example data or public/uploads. The root directory is shown in front of the field for monorepos.

  • Up to 20 paths per app.
  • Paths can't be inside each other: data and data/blog can't both be listed.
  • Use letters, numbers, dots, dashes and underscores. Paths can't start with / or contain ...

To stop keeping a folder, click the bin next to it. That applies when you save.

Step 3 Save and redeploy

Click Save build settings, then Redeploy to apply. The next deploy moves the folders into shared storage and links them into every release from then on.

When Nuvlo finds unknown folders

Before each deploy, Nuvlo compares the running release with the code it was built from. If the app wrote files into a folder that isn't a persistent path, the deploy pauses before anything changes and gets the status Action required. The current release stays live.

Persistent storage then lists each folder with its number of files and size. For each one, decide:

  • Make persistent keeps all listed folders in shared storage, starting with the next deploy. Choose this for uploads, databases and content.
  • Ignore treats a folder as disposable; it may be replaced on each deploy. Choose this only for cache, log or temporary folders.

Once every folder is classified, redeploy. Ignored folders are listed under Ignored, may be replaced during deployments; click the cross next to one to have Nuvlo check it again on the next deploy.

ImportantAn ignored folder's data can be lost with the next deploy. If unsure, choose Make persistent.