This week's podcast, episode 56, has Greg Anderson and Juampy Novillo Requena join Addison Berry to discuss Drush and the PHP dependency manager, Composer. We talk about what Drush and Composer are, why and how Drush is using Composer now, as well as a look down the road at further integration.
When I first started learning Drupal, I remember the process of enabling and disabling modules on the Modules page took for-ev-er. My laptop was in serious danger of getting hurled across the room, due to my frustration. Then I discovered drush, and downloading and enabling modules was now performed with ease instead of pain and suffering. Of course there's a lot more you can do with drush than just download and enable modules, this is just one example.
It's been a really long time since I've worked on a Drupal build that didn't make use of the features module in some way or another. For better or worse it's turned into one of those modules like Views that's simply a part of the expected toolkit for many projects. Yet I still occasionally meet people who haven't heard of it yet.
This week, we are wrapping up 2012, and our Coding for Drush series. The last videos in this Drush series will take a look at some really neat things you can do with your new-found Drush skills. The first thing we want to look at is creating policy files for your Drush command. This allows you to essentially provide access control for your commands. You can check who is trying to run the command and stop it from proceeding. After we get that in place, we wrap up with two videos about Drush make.
As we work our way through December, we are also working our way through the Coding for Drush series. This week we have three new videos, which cover a bunch of extras to add to our drush command. We'll be looking at how to add additional help information, and prompt the user for more information. Then we'll take a dive into some more advanced things with specifying version numbers, and even the Drupal bootstrap level required.
With today's release we are keeping the Coding for Drush series rolling. We will get into making our new Drush command actually do some work for us, and then allow our command to take arguments and options. We'll talk about what the differences are between arguments and options, and then implement them in our work.
This week we're releasing a new series, Coding for Drush. If you've ever used Drush, and wondered how you can create your own custom Drush commands, then this series is right up your alley. When I sat down to start planning the content for our recent Coding for Views series I found myself in a position where I needed to quickly generate a bunch of random data for a custom module’s database table, so that when querying the table with views there would be something there.
For the Module Development series, we are wrapping up the discussion of the Render API with a look at integrating with the theme system. Then we move on to four videos about the Form API system and how to do some fun things with it:
Experienced developers, and new site builders alike can remember a time when installing a module meant visiting it's project page on drupal.org, downloading and unpacking it and dropping it in the correct directory. That process can be quite tedious every time there's an update if your site has dozens of modules. Thank goodness for drush. While drush's utility certainly isn't limited to helping download modules for your site in an efficient manner, it's an absolutely invaluable tool for anyone working with Drupal sites on a regular basis. We're happy to present a new series, Introduction to Drush, with the first video, What is Drush?, released today.