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

Feature: Specify config file #8

Open
ghost opened this issue Aug 16, 2011 · 4 comments
Open

Feature: Specify config file #8

ghost opened this issue Aug 16, 2011 · 4 comments

Comments

@ghost
Copy link

ghost commented Aug 16, 2011

Hi

It would be great to be able to specify the db_config file in the command line so that the same install can be used for multiple projects.

I don't think this is done already but I think it would be a good feature.

Thanks for your work.

@davesloan
Copy link
Owner

That's a good idea. I'm thinking of changing the config so that it can use as many "environments" as you want and you specify the environment when running the command.

@ghost
Copy link
Author

ghost commented Sep 13, 2011

Cool, I got something working to suit what I needed. I'll tidy it up and submit a pull requests so you can see if is what you would do or you can ignore it.

@bgonderi
Copy link

I would be very interested in this functionality as well (or an explanation of how to work around not having it). I assume I could create multiple config/db_config.php files (one for prod, one for dev, etc.), and then when I pull a copy, manually copy or link one of them to db_config.php.

@ghost
Copy link
Author

ghost commented Feb 23, 2012

Oh I just realised I said I would submit code for this!

I will get to this.

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