Skip to content
Menu
DocumentationPersistent storage
Application management

Persistent storage

Write files that must survive deployments to /var/opt/lei. All packages in the workspace share this directory. Applications start in /opt/lei, the source directory; use an absolute data path for uploads, SQLite databases, and other persistent files. Builders cannot access the live data directory.

Files in /tmp and the home directory outside the Cargo cache are temporary and disappear when the VM stops. Changes made in Terminal are not Git commits. Keep source and configuration changes in your local project and deploy them with Git.

The production workspace storage limit is 20 GiB, shared by source, Cargo cache, application data, PostgreSQL data, and allocated swap. Dashboard shows storage usage and a breakdown; swap uses host disk as pages are written, rather than reserving its full capacity. A full quota can prevent builds or database writes. Free space and redeploy after resolving the failure.

Keep backups of persistent files and databases. PostgreSQL has no automated backup or restore workflow.