My SQLite database resets after every deploy.

The short answer

SQLite keeps its whole database in a file next to your app. On Antideploy, the disk that file lands on is temporary: it is wiped whenever the app restarts, redeploys or scales to zero. Nothing errors, and the data is simply gone. Move to Postgres. Antideploy creates one beside your app, and it survives every deploy.

How to tell

• A .db or .sqlite file, or better-sqlite3 or sqlite3 in your code. Antideploy flags SQLite before it builds, because the app deploys fine, reports healthy and loses data.
• Your data is back to the starting state after a deploy. Users, rows or settings reset.

How to fix it

1. Ask your agent to switch to Postgres

   Say: "Replace SQLite with Postgres." Your agent creates the database, sets DATABASE_URL and changes the code. Antideploy can create the database for you, but the code has to be changed to use it.

2. Move any existing data

   Export the rows you want to keep from the SQLite file, and import them into Postgres.

3. Deploy

   The database belongs to the application and every deploy reuses it. Only the container's disk is replaced.

See how to add a Postgres database to your app.