adding configuration option to use different migrations directory#58
Open
skecskes wants to merge 1 commit intoafloyd:masterfrom
Open
adding configuration option to use different migrations directory#58skecskes wants to merge 1 commit intoafloyd:masterfrom
skecskes wants to merge 1 commit intoafloyd:masterfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi,
I had lately issue with migrations, because the config file and migrations file are in different folders. I couldn't use even current working directory because that broke paths in configuration file require statements. The only solution for me seems to have special parameter to define migrations folder separately, same as config file is defined separately. Please, can you accept this merge request and then update the npm too?
Btw, thanks a lot for repo. It saves me lot of time. :)