<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Drush on Mike Bell - Blog &amp; Stuff</title><link>https://mikebell.io/tags/drush/</link><description>Recent content in Drush on Mike Bell - Blog &amp; Stuff</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>hello@mikebell.io (Mike Bell)</managingEditor><webMaster>hello@mikebell.io (Mike Bell)</webMaster><copyright>© 2026 Mike Bell</copyright><lastBuildDate>Thu, 24 Apr 2014 00:00:00 +0000</lastBuildDate><atom:link href="https://mikebell.io/tags/drush/index.xml" rel="self" type="application/rss+xml"/><item><title>Quick and Easy Drush Debian Packaging</title><link>https://mikebell.io/posts/quick-and-easy-drush-debian-packaging/</link><pubDate>Thu, 24 Apr 2014 00:00:00 +0000</pubDate><author>hello@mikebell.io (Mike Bell)</author><guid>https://mikebell.io/posts/quick-and-easy-drush-debian-packaging/</guid><description>
&lt;p>I found a really nice way of packaging up drush as a debian package without having to go through all the hassle of creating all the files for a “true” debian package.&lt;/p>
&lt;p>You’ll need the following:&lt;/p>
&lt;ul>
&lt;li>Git&lt;/li>
&lt;li>Composer&lt;/li>
&lt;li>FPM gem&lt;/li>
&lt;/ul>
&lt;p>You can then run the following commands to setup your base environment for packaging:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-shell" data-lang="shell">&lt;span class="line">&lt;span class="cl">git clone git@github.com:drush-ops/drush.git
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="nb">cd&lt;/span> drush
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">composer install
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">sudo gem install fpm
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>To test to make sure your latest master copy of drush is working quickly run either &lt;code>drush&lt;/code> or &lt;code>drush —version&lt;/code>&lt;/p>
&lt;p>Now you are ready to package the contents up:&lt;/p>
&lt;p>&lt;code>fpm -s dir -t deb -n drush -v master ./drush=/usr/bin&lt;/code>&lt;/p>
&lt;p>What this does is tell fpm you want to create a deb file from a directory with a version name of master (corresponding to the branch we checked out in git), it also configures the output directory.&lt;/p>
&lt;p>Once that’s run you should see the newly created package appear. To verify it’s contents run &lt;code>dkpg -c drush_master_amd64.deb&lt;/code>&lt;/p>
&lt;p>Throw in a parameterised job in jenkins and you have a nice way of creating version specific debian packages for deployment.&lt;/p>
&lt;p>Thanks for reading via RSS!&lt;/p>
&lt;p>Send me a message on &lt;a href="https://remotelab.uk/mikebell">Mastodon&lt;/a> or &lt;a href="mailto:hello@mikebell.io">email me&lt;/a>&lt;/p></description></item><item><title>Override servers version of drush</title><link>https://mikebell.io/posts/override-servers-version-of-drush/</link><pubDate>Thu, 23 Jan 2014 00:00:00 +0000</pubDate><author>hello@mikebell.io (Mike Bell)</author><guid>https://mikebell.io/posts/override-servers-version-of-drush/</guid><description>
&lt;p>Recently I had to work on a server that was heavily restricted by a third party company. They were using an archaic version of drush so I decided to change it!&lt;/p>
&lt;p>I have no access to sudo or any form of root account, this made things even more interesting. No wget either.&lt;/p>
&lt;ul>
&lt;li>Download drush 6.2.0 to local machine&lt;/li>
&lt;li>Download console_table 1.1.3 (has to be this version)&lt;/li>
&lt;li>&lt;code>scp&lt;/code> both drush and console_table to remote server&lt;/li>
&lt;li>&lt;code>unzip&lt;/code> drush to ~/drush-6.2.0&lt;/li>
&lt;li>&lt;code>tar -zxf&lt;/code> console_table to ~/drush-6.2.0/lib/&lt;/li>
&lt;li>modify .bashrc / .zshrc and add the following:
PATH=&amp;quot;/home/badger/drush-6.2.0:$PATH”
export PATH&lt;/li>
&lt;li>&lt;code>source ~/.bashrc&lt;/code> or &lt;code>source ~/.zshrc&lt;/code>&lt;/li>
&lt;/ul>
&lt;p>There you go the latest version of drush on a locked down system.&lt;/p>
&lt;p>Thanks for reading via RSS!&lt;/p>
&lt;p>Send me a message on &lt;a href="https://remotelab.uk/mikebell">Mastodon&lt;/a> or &lt;a href="mailto:hello@mikebell.io">email me&lt;/a>&lt;/p></description></item><item><title>Download Drupal to Current Directory using Drush</title><link>https://mikebell.io/posts/download-drupal-to-current-directory-using-drush/</link><pubDate>Tue, 27 Aug 2013 00:00:00 +0000</pubDate><author>hello@mikebell.io (Mike Bell)</author><guid>https://mikebell.io/posts/download-drupal-to-current-directory-using-drush/</guid><description>
&lt;p>This has always bugged me, you can&amp;rsquo;t easily download Drupal to your current directory using drush. After a quick search I found this issue - &lt;a
href="https://drupal.org/node/495438"
target="_blank"
>https://drupal.org/node/495438&lt;/a>&lt;/p>
&lt;p>The following command works well -&lt;/p>
&lt;pre>&lt;code>drush dl -d --destination=&amp;quot;..&amp;quot; --drupal-project-rename=&amp;quot;$(basename `pwd`)&amp;quot;
&lt;/code>&lt;/pre>
&lt;p>So what&amp;rsquo;s it doing?&lt;/p>
&lt;ul>
&lt;li>&amp;ndash;destination - specifies where to download Drupal to&lt;/li>
&lt;li>&amp;ndash;drupal-project-rename - renames the downloaded directory to your current directory&lt;/li>
&lt;/ul>
&lt;p>Thanks for reading via RSS!&lt;/p>
&lt;p>Send me a message on &lt;a href="https://remotelab.uk/mikebell">Mastodon&lt;/a> or &lt;a href="mailto:hello@mikebell.io">email me&lt;/a>&lt;/p></description></item></channel></rss>