Grayside wrote a blog on how to do this: http://grayside.org/node/93.

It's a good idea. We could either add it to example.drushrc.php, as shown (included with permission), or perhaps make it standard functionality in drush_bootstrap_drush. The advantage of just making it a sample is that it is more flexible vis-a-vis repository layout.

CommentFileSizeAuthor
grayside-config-from-git-example.patch801 bytesgreg.1.anderson

Comments

greg.1.anderson’s picture

greg.1.anderson commented
Status: Needs review » Needs work

I thought it was a good idea to use 'drush_shell_exec' here, just to use the drush API, but doing it this way does not work well when running drush with --simulate. I think grayside had the right idea calling exec directly.

moshe weitzman’s picture

moshe weitzman commented
Status: Needs work » Patch (to be ported)

I like this too and agree with putting it in example.drushrc.php. committed with exec().

Commit 1adf73a if we want to backport. Seems desireable.

msonnabaum’s picture

msonnabaum commented
Status: Patch (to be ported) » Fixed

Backported.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.