Closed iduuck closed 8 years ago
Looks like @pioneerskies merged a pull request recently, maybe it still is maintained, just not on a frequent basis. I would suggest create a pull request or issue regarding the .env support.
Surely iDuuck is referring to already available features? you can define different environment variables really easily.
e.g. Push database to staging:
wordmove push -e staging -d
or Pull database from production:
wordmove pull -e production -d
Just define them in the referenced docs in your Movefile.
It's not that I want to adjust the vhost and wordpress_path of the production/staging environment, but for the local environment. For example if I am working on an Wordpress installation from two people.
So I would assume something like
local:
local: enviroment_vars.local
wordpress_path: environment.wordpress_path
[...]
Hi @iDuuck I'll try to aswer to questions. WordMove is still maintained, not frequently but maintained. We hope that developers community contributes to WordMove growth. If you want an additional feature to WordMove about .env vars support you must to open a specific issue and/or make a pull request. Reopen the issue if needed.
So, the commit history states, that the development of wordmove isn't very active in the last time. If this project isn't in active development anymore I am forced to switch to another solution or write my own. Would be sad, because I think there were many work into wordmove.
But the feature I am missing most is
.env
support.