Skip to content
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

Multiple environments (dev, stage?) for a single project using different config files/directories #939

Closed
jdoubleu opened this issue Jun 22, 2018 · 2 comments

Comments

@jdoubleu
Copy link
Contributor

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.

@rfay 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
@rfay rfay added the hibernate label Jun 26, 2018
@rfay
Copy link
Member

rfay commented 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?

@jdoubleu
Copy link
Contributor Author

That would be a solution, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants