-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Specifying a target Migrations directory. #24
Comments
When I started working on this I just enabled what is mostly critical for apps to work and just went with it. So yeah there are a couple of hard coded stuff. I planed on enabling more features in the underlying migrator but I just didn't see an actual necessity. But It has been a while since I did a review on this so I guess I should do a couple of those little wanted features and do an update. Keep this open and I'll let you know when I update. |
Awesome thanks! |
Okay, so. You'll have to specify your migrations dir in both the So:
|
Yes ... that seems like the MS implementation (according to their docs). |
I'll let you know when I do a package update. (probably very soon) |
Killer, thanks! |
@AlonCG |
Awesome! Thanks again and could not have even dreamed of a better response time! I will try it out in a few minutes. |
Haha don't worry about it. Glad to help. |
Thanks again ... "-o" working so far! |
Is it possible to specify a target Migrations directory?
Currently ... even when my configuration lists a non-default ("Data\Migrations") folder, the migrations are still added to the default "Migrations" folder.
I see in your "Executor" that the folder appears hard-coded, any way to add a switch to enable another location? It is not overly critical, as I can just move the migrations, but it would be nice.
Thanks for all your work and assistance.
The text was updated successfully, but these errors were encountered: