-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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.
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
Docs: Move Migrations out of Extensions #21719
Conversation
🦋 Changeset detectedLatest commit: ba4bd0a The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thank you! ❤️
Just a small change request:
This newly introduced config option MIGRATIONS_PATH
has a default of ./migrations
, so there's usually no need to explicitly define the option, migrations can just be placed in this folder.
With the defaults configs, this means the folder is expected to live at the same level as the extensions
folder:
├── extensions
└── migrations
…directus into docs/migrations-not-extensions
How's that @paescuj |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How's that @paescuj
Perfect 😘👌
Docs for #20626