Exporting your project and moving it elsewhere

Nothing here is locked in. There are three ways out.

1. Full project ZIP

Code tab → Export ZIP gives you every source file, a generated README, a .env.example, and your live database. Unzip it on any server, npm install, start it, and the app runs with its existing data.

2. Database only

Database tab → Export downloads the SQLite file. Per-table CSV and JSON export is also available for moving data into another system.

Exports are taken as a consistent snapshot, not a file copy. That matters: these databases run in WAL mode, where recent writes live in a side file, so a naive copy can produce a database that will not open.

3. GitHub

Connect GitHub and every generation becomes a real commit. See Connecting GitHub.

What is deliberately excluded

• .env — real secrets. Never committed. Use the generated .env.example.
• node_modules/ — reinstallable with npm install.

The database is in the ZIP but not in GitHub, because it holds your users' personal data and git history is permanent. Your schema lives in db.js, so a fresh clone recreates the tables automatically.