Description
This module allows to run Drush without being granted access to the machine it relies on. It may be useful on shared hosts that do not provide SSH access to servers.
Example:
* With Drush (regular), one connects to a server using SSH and runs: drush en views.
* With this module, one uses Drush on his own workstation and runs: drush @myserver web en views.
Requirements
| Server | Client |
|---|---|
|
|
Quick installation
- On the server:
- Enable modules
drushwebandoauth_common_providerui. wget https://github.com/drush-ops/drush/archive/7.x-5.9.zipunzip 7.x-5.9.zipmv drush-7.x-5.9/ sites/all/libraries/drush- Go to
/admin/reports/statusand make sure Drush is detected. This path needs to be valid:sites/all/libraries/drush/drush.info. - Grant yourself role
Drush Webservice OAuth user. - Go to
/user/[your-uid]/oauth/consumer/addand add a consumer with callbackhttp://example.netand contextDrush Webservice. Note the key and the secret.
- Enable modules
- On the client:
- Edit
~/.drush/aliases.drushrc.php
$aliases['myserver'] = array( 'uri' => 'http://example.net/myserver', // Your server URI. 'oauth_key' => 'y4ZYMrw8VNMDsnkibMxwu8ZybS4GPzHV', // Your OAuth key. 'oauth_secret' => 'JHjnXtfpLxrPCVwnjyn8dCQmsxNmgfEZ', // Your OAuth secret. ); cp -R drushweb/ ~/.drush/drushwebdrush cache-clear drushdrush @myserver web en views --yes. Views should get enabled on the server and the command output should show up.
- Edit
Please also have a look at sections 'Making the client user friendly' and 'Security considerations' in README.txt.
Step-by-step installation
See README.txt.
Related projects
- Drush webservice API: https://github.com/drush-ops/drush/pull/405
Project information
Maintenance fixes only
Considered feature-complete by its maintainers.- Project categories: Administration tools
1 site reports using this module
- Created by fengtan on , updated
Stable releases for this project are covered by the security advisory policy.
There are currently no supported stable releases.

