feat(database): add support for multiple database migrations directories #423
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #401
With this PR, NuxtHub scans the
server/database/migrations
directory for migrations for each Nuxt layer.If you need to scan additional migrations directories, you can specify them in your
nuxt.config.ts
file.NuxtHub will scan both
server/database/migrations
andmy-module/db-migrations
directories for.sql
files.If you want more control to the migrations directories or you are working on a Nuxt module, you can use the
hub:database:migrations:dirs
hook:All migrations files are copied to the
.data/hub/database/migrations
directory every time you run Nuxt. This is useful to see all migrations applied in the database as well as running thenpx nuxthub database migrations <command>
commands.