-
Notifications
You must be signed in to change notification settings - Fork 71
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
Add migrations path to config #64
Comments
I've found that inconvenient as well. In the As far as also putting it in the config, it's possible. But one annoying issue is how to handle relative paths. Is it relative to the config file or the working directory tern is run from? |
Is it allowed to have relative path for config in |
Yes. That's exactly what I do. My
|
Given that tern must be run in the same directory as the config file (when not using The Would this work:
|
Concider documenting it |
My use case: I always run
tern <command> --migrations ./migrations ...
so the config is in the root of the project and migrations are in./migrations
.So I would like to omit
--migrations ./migrations
when calling commands. What if we can have it in the config?The text was updated successfully, but these errors were encountered: