I need to be able to to run queues in a situation where I cannot modify my home directory and I need to run these queues from the server by this user via crontab. By adding a .module file you can enable this as a module and then run your queues. The drush_queue.module can be empty- it seems like it just needs to exist.

Comments

msonnabaum’s picture

msonnabaum commented
Status: Active » Postponed (maintainer needs more info)

So you can't install in either /usr/share/drush/commands or ~/.drush?

I specifically didn't add a .module, because that makes drush download the project as a module as opposed to globally. I'd rather not break that for everyone else.

I'm open to other ideas to make this easier, I'm just not sure what the best course would be.

becw’s picture

becw commented

The current use case for this is with Acquia hosting--we can't write to our user directory, and the queue-* commands aren't working remotely (drush 4.5 with aliases), so the only way we can use drush_queue there is to have it installed on the site as a module.

msonnabaum’s picture

msonnabaum commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

I've started this issue in the drush queue to allow loading command files from the project root to get around this issue:

http://drupal.org/node/1370956

If that gets it I will most likely backport it to drush4 as well.

In the meantime, just add a .module in your repo and enable it. SHould work then.