Recent Story Comments en Thanks for the comments! I've <p>Thanks for the comments!</p> <p>I've updated the article to note DBN instead. Of course, the delay is actually with me as it turned out that my web server didn't have enough disk space to store the video, so I'll have to wait until I get back to Guelph to upload the screen capture.</p> <p>I've actually thought about making this into a proper Drush script, but I'm waiting for full command aliasing support to hit. That way, you'll be able to override the built-in commands with a custom script, so running <code>drush dl views</code> would actually copy it from your vendors repository instead. And then, you could even make external tool configurations in Eclipse to have a GUI for installing and updating modules in your local copy.</p> Mon, 19 Oct 2009 15:41:11 +0000 andrew comment 223 at Good Job! <p>Hello Andrew,</p> <p>Good job with your presentation.</p> <p>I think the video team is DBN and not DCM.</p> <p>@Nick_vh: The script that he propose does more than Drush. Drush does not add the downloaded module to a vendor branch for keeping track of changes across multiple websites easily. As Andrew mentioned in his presentation, using vendor branches will not be useful for people that only maintain one website. His script might not apply to you. It is true that Drush does other things that his script is not doing.</p> <p>@Andrew: How about getting your code into a drush script? :)</p> Mon, 19 Oct 2009 13:08:45 +0000 Christian Roy comment 222 at Drush <p>I don't understand why u use your own script instead of using Drush? Also in your presentation I don't see anyreference to the drush module? I would like to recommend you to look at it because it enables you to do all of this (module download from cvs) and much much more!</p> <p>Nice presentation though! Thx!</p> Mon, 19 Oct 2009 07:25:04 +0000 Nick_vh comment 221 at