Support env.local, et al. or support --envfile
CLI option
#354
Replies: 7 comments 2 replies
-
I also would like this issue supported |
Beta Was this translation helpful? Give feedback.
-
Happy to accept a PR for this, I think it would only be a few lines of code |
Beta Was this translation helpful? Give feedback.
-
I haven't written any go code, but if this is still sitting open in a week or two, I may give it a try. Also, if anyone does write a pr, I would definitely prefer the solution of
|
Beta Was this translation helpful? Give feedback.
-
I'd love this too. |
Beta Was this translation helpful? Give feedback.
-
Looks like something like |
Beta Was this translation helpful? Give feedback.
-
I fixed it in this pr #491 |
Beta Was this translation helpful? Give feedback.
-
For everyone who is interested in this feature, please take a look at #491. Specifically, the behavior when the specified file does not exist, where we silently ignore and continue, and the behavior when multiple files are specified by repeating The tests illustrate the expected behaviors: Lines 63 to 180 in 857ffed |
Beta Was this translation helpful? Give feedback.
-
dbmate does not support additional
.env
files, e.g..env.local
or.env.development.local
due to joho/godotenv#10Possible solutions of varying completeness:
loadDotEnv
also load.env.local
--envfile
option which specifies file forgodotenv.Load()
Beta Was this translation helpful? Give feedback.
All reactions