Posted by Chris Charlton on September 10, 2010 at 8:43pm
I'd like to start a dialog here about what is slated to be in Drush 4.0, as the HEAD release is 4.0-dev.
Drush 4.0
Group organizers
Hot content this week
-
2 days 14 hours ago
-
1 week 14 hours ago
Comments
A new 4.0 feature, a proposed 4.0 feature
See:
http://drupal.org/node/908212
http://drupal.org/node/861822
http://drupal.org/node/446736
As 4.0 development progresses, you might want to monitor the new committed features in HEAD:
http://drupal.org/project/issues/search/drush?status[]=2&status[]=7&categories[]=feature&issue_tags_op=or
"I like this feature or that feature" is a good topic for this thread; support and feature requests are best brought up in the issue queue.
Standard paradigms encouraged
My two cents are not so much with functionality, but rather, "non-functional requirements" in terms of usage and documentation. Specifically, adopting a design paradigm for using drush in a way that's consistent with other command-line utilities, using GNU & Unix as a model. Small examples:
Show the actual software version, including VCS revision IDs:
$ drush --version
# -- Current approximation:
$ drush status version
Show help info, regardless of Drupal site location or availability:
$ cd /tmp
$ drush sql-dump --help
# -- Current approximation:
$ drush -r /Applications/MAMP/htdocs/my_site sql-dump --help
Read from "standard input" (STDIN):
$ cat - <<EOF | drush -r /Applications/MAMP/htdocs/my_site scr -> <?php echo "test\n"; ?>
> EOF
test
Ensure Drush et al is adequately robust, secure, & functional to be installed as a regular utility:
$ grep Smart /usr/local/drush/commands/drush_make/INSTALL.txt
- In /path/to/drush/commands (not a Smart Thing, but it would work).
# Now why is that?
Reformat the help text into a man page:
$ man drushNo manual entry for drush
BTW - These comments are meant to be constructive, not critical! I appreciate how much good work you guys have done in this area. At some point, I hope to be in a position to make useful contributions myself. Thanks.
new and proposed features in Drush 4.x
I am a fan of the proposed DB Sanitization of user data during sql-sync.
Ignoring a module (hacked or not) is also going to be great for developers/maintainers.
Chris Charlton, Author & Drupal Community Leader, Enterprise Level Consultant
I teach you how to build Drupal Themes http://tinyurl.com/theme-drupal and provide add-on software at http://xtnd.us
Module ignores work! (update_advanced)
You can do this with the update_advanced-module. drush will respect the settings, since it uses the update-module for the updates (update and update_advanced were the same module in D5). If I read and understood this issue correctly, even drush developers are unaware of this.
Surprisingly, this feature is not documented anywhere, atleast not in drush or update_advanced's (!) issue queues (drush & update_advanced).
It's very usefull, we have been using it in our workflow for over a year now. I believe a lot of people would, if this was somehow documented.
man drush
Leveraging standard linux formatting would be quite useful.
I would gladly work on a drush man page.
Is that desired by the maintainers of drush?
What is best way to contribute to drush project dev?
Thank you!
Jeremy Donson
Database and Systems Engineer
New York City
Great Idea!
Great Idea!
RE: man drush
Hi jdonson,
It'll be great to have a good drush manual page! With ubuntu, you can already install drush with a simple 'apt-get install drush', so maybe there is an already done initial man page.
See you!!
emi
$ sudo yum drush repos: 3.x, 4.x, 5.x
I propose three drush repos for
$ yum install drush
Any thoughts / insights / questions about the mini-roadmap below would be great!
LEGACY:
I was able to install drush 3.x on CentOS 5.x using rpmbuild.
http://www.workhabit.com/labs/drush-rpm-form
This supports Drupal 5.x forward, so that is useful!!
However, the extended features in drush 4.x and 5.x are JUICY! :D
http://cyrve.com/drush4
CURRENT:
Need to find similar recipes and ingredients for drush versions 4.x and 5.x.
Then, as suggested, I would like to start to contact maintainers
and survey debian drush package repos for man and other supporting doc features.
EMERGING:
http://groups.drupal.org/node/93449
Jeremy Donson
Database and Systems Engineer
New York City
The new standard for
The new standard for installing drush is pear; details can be found on the Drush project page. As you can imagine, supporting package managers for many different distros (apt-get, yum, yast, Windows) for multiple versions of Drush would take a lot of work from a lot of different volunteers. While providing these packages would certainly be helpful, keeping the pear distros up to date is much more tractable, and will work cross-platform. Of course it is also possible, and quite convenient, to install drush from git, which is recommended for those interested in submitting patches to the drush issue queue.
Regarding Drush documentation, there is a lot of information in Drush itself that can be found in the output of
drush helpanddrush topic. A lot of this information can be found on http://drush.org. The html-format of thedrush helpoutput on drush.org is produced programatically viadrush help --html. If someone were to undertake the task of creating a Drush man page, it would be advisable, I think, to do something similar and build the contents of the man page by formatting the output ofdrush helpanddrush topic. Otherwise, it would be difficult to keep the man page up to date with the most recent version(s) of Drush.pear did not work and rpms did
Thanks for clear answers.
That sounds great and makes sense, but the instructions for pear install were
followed to the letter and that method failed. :(
I would prefer to manage yum rpms for the linux community. Why not?
Including standard man pages and yum linux support seems like a logical next step.
Simply want them for CentOS/RedHat platform, which is dominant in Enterprise.
I agree that the man page should be a reformatting of help.
regards
Jeremy Donson
Database and Systems Engineer
New York City
drush 4.x rpms....
http://www.ruslansivak.com/2011/1/5/Drush-rpm-for-CentOS-55-and-probably...
This was helpful for managing 4.x rpms for drush.
Drush 4.x auto-updated itself on CentOS 5.x:
$ drush --version
drush version 4.0-rc9
A newer version of drush, 7.x-4.5, is available. Would you like to back up your current drush, version 4.0-rc9, to /root/.drush-backups/20111108123949 and replace it with the newer release? (y/n): y
drush backed up to /root/.drush-backups/20111108123949/drush [ok]
Project drush (7.x-4.5) downloaded to /usr/local/drush. [success]
Drush successfully updated to version 7.x-4.5. [success]
Jeremy Donson
Database and Systems Engineer
New York City
Great discussion, but it
Great discussion, but it would be good to move to the issue queue. The self-update feature you quote above was removed in drush-5.x in favor of the pear distribution method. If pear isn't working for you, perhaps you could post an issue in the queue.
k - will try
thx
Jeremy Donson
Database and Systems Engineer
New York City