Earlier this week I gave a drush demo to some people in another division of my company. A key step in setting up site aliases to talk to remote servers (pardon the pun) is the establishment of public / private key pairs to protect the ssh transport that drush uses during syncs and executing remote commands.
To make this easier, I use a bash script called "pushkey"; after this demo, it occurred to me that having pushkey available as part of drush core would be very convenient. So, although public / private key initialization is not Drupal-specific, it is an integral part of a Drupal / drush system setup; I therefore propose that the pushkey command be added to drush core.
Enclosed is the version of pushkey that I ported from bash to a drush command. This file is currently living in my .drush folder (rename from ".txt" to ".inc"). If you agree, I'll move it into drush core, integrating it a-la drush rsync.
| Comment | File | Size | Author |
|---|---|---|---|
| pushkey.drush_.txt | 3.03 KB | greg.1.anderson |
Comments
Comment #1
moshe weitzman commentedI'm not really inclined to support this code in drush project. Sure it would help a lot of people, but it would generate loads of support tickets as well. Perhaps you want to create a d.o. project for it and we can link to it from various drush docs.
I'm willing to change my mind based on input from other maintainers.
Comment #2
greg.1.anderson commentedSupport tickets... hmmm.
What if we made a folder 'examples/commands', and put things like pushkey and site-sync there? The folder could contain a README instructing users to copy commands they want to use to $HOME/.drush, and include a disclaimer that the scripts were examples only, might need customization to match the user's particular configuration, and are unsupported.
Would that work?
Comment #3
moshe weitzman commentedThat doesn't really work for me, sorry. Folks will still ask for help. And then we have to help folks get over of the examples/commands hurdle. Its good and useful software, but I have to draw the line somewhere. As I said, I'd prefer to externally distribute pushkey and link to it from all over (assuming it carries its own issue queue. otherwise, drush gets the queries).
Comment #4
greg.1.anderson commentedSure, that's no problem.
One more question, though. Pushkey seems too small of a script to warrant its own project. How about if I take over drush_extras instead, and put auxiliary commands there?
Comment #5
moshe weitzman commentedFine with me. I've made you owner.
Comment #6
greg.1.anderson commentedThank you very much. Moving on over to the Drush extras queue...
Comment #7
greg.1.anderson commentedCommitted.