Skip to content

doc: development notes on migrations #120

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
robsimmons merged 1 commit into from
Sep 9, 2026
Merged

doc: development notes on migrations #120

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ node_modules/

# prisma
**/prisma/generated
/.temp-for-migrations.db

# production
/build
Expand Down
10 changes: 10 additions & 0 deletions doc/DEVELOPMENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,6 +96,16 @@ This is because containers run in Linux VMs,
where virtual filesystems such as virtiofs cause degraded disk IO performance
and might not support overlayfs.

## The database schema

The database schema lives in `src/prisma/schema.prisma`.
If it is changed, you'll need to use Prisma to create migrations using a temporary database.

```sh
DATABASE_URL="file:$PWD/.temp-for-migrations.db" npx prisma migrate dev
rm ./.temp-for-migrations.db
```

## Debugging

In dev mode (`make dev`),
Expand Down
Loading