You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like
I'd like to be able to set a (different) config path for the ddev command.
Just like docker-compose support an option to define a different config file.
I could imagine something like ddev --config=.ddev_other_env and ddev would use the .ddev_other_env/ directory.
It would be possible to test the application in different environment.
E.g. different php versions, future but yet unstable php features, MySQL vs MariaDB, etc.
Describe alternatives you've considered
At the moment one can parameterize the .ddev/config.yml and use a bash script to modify the config.
But this approach is error prone and might lead to unexpected behavior. Especially when (accidentally) changing the config while ddev is running.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
rfay
changed the title
Multiple environments using different config files/directories
Multiple environments (dev, stage?) for a single project using different config files/directories
Jun 26, 2018
One thing you might consider doing is having two projects, check out the branch you want for each. So two git checkouts, configured with different project names. They'd have completely different databases. Would that solve the problem described here?
Describe the solution you'd like
I'd like to be able to set a (different) config path for the ddev command.
Just like
docker-compose
support an option to define a different config file.I could imagine something like
ddev --config=.ddev_other_env
and ddev would use the.ddev_other_env/
directory.It would be possible to test the application in different environment.
E.g. different php versions, future but yet unstable php features, MySQL vs MariaDB, etc.
Describe alternatives you've considered
At the moment one can parameterize the
.ddev/config.yml
and use a bash script to modify the config.But this approach is error prone and might lead to unexpected behavior. Especially when (accidentally) changing the config while ddev is running.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: