Fix and expand "Configuring migrations" section in README #237
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix a mistake with the `knex migrate` command (shouldn't have `npm run` in front of it) and add section about updating config so migrations work.
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix a mistake with the
knex migratecommand (it shouldn't havenpm runin it) and add a section about updating config so migration creation works.I changed the database adapter in the example from
mysqltopostgresbecause the config I had readily available is for postgres, and I wanted the example knexfile to match the config example I added.Background:
I was reading #116, which led to #225. My PR improves upon 225.