Persistent volumes, file mounts and volume backups

The container filesystem resets on every deploy. Data written outside a volume (uploads, SQLite files) is lost. Use a volume, a managed database or object storage.

Add a volume

1. General → Persistent Volumes → + Volume: a unique name (e.g. data) and container path (e.g. /app/data).
2. Save, then Deploy.

Volumes survive deploys, restarts and stop/start. Host folder mounts aren't supported.

Mount a config file

+ File mount: name, container file path (e.g. /etc/nginx/nginx.conf) and content. Save, Deploy. File mounts are read-only and rewritten from the saved content on each deploy.

Removing a volume

Removing a saved volume asks you to confirm Detach; after the next deploy the app no longer sees that data. Back it up first.

Volume backups

1. Project Volume Backups tab: pick a volume, Create backup.
2. Restore replaces the volume's current data and restarts the app.
3. Delete old backups from the list.

Backups are on demand. For scheduled backups use a managed database's automatic backups or a cron schedule that exports data.

Advanced → Delete app removes the app's containers, domains, deployments and volumes permanently, so back up first. Preview deployments don't mount volumes.