Skip to content

Add troubleshooting hint regarding migrations #77

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
sebmue-dataport merged 2 commits into from
Jan 27, 2026
Merged

Add troubleshooting hint regarding migrations #77

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7d473f4
add hint
sebmue-dataport Jan 8, 2026
57ac699
Merge branch 'main' into initial-setup-hint
sebmue-dataport Jan 27, 2026
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
3 changes: 3 additions & 0 deletions docs/backend/Migrations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,3 +98,6 @@ Commit the changes:

- By their nature, migrations become outdated as the database model changes. You are never expected to update migrations due to any changes in the code that are made.
- If needed, for example because the migration shows errors due to a code (model) changes, migrations can be deleted, since they will still be accessible in the git history.

#### Initial setup failure
- If the initial setup using `npm run setup:db:seed` and `npm run migration:up` fails you may want to delete the `dist` folder and try again.