-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow downloading to '/modules' within multisite setup #197
Comments
Marking this as a bug as I was able to do the following:
|
It just occurs to me that Backdrop is quite different to D7 in how its multisite system works... In Backdrop, if you don't have a multisite setup then you're using the In D7, regardless of whether you have a multisite setup or not, you're using Therefore, as far as Drush is concerned, the different between multisite and non-multisite in D7 is negligible. However in Backdrop it's quite a big difference. It seems then that Backdrop's Drush extension will need quite a bit of re-writing to properly support Backdrop's multisite setup. I will try my best to see if I can contribute to this effort, but I'm finding Drush quite a hard beast to tame. Maybe a 'Drush Lite' for Backdrop is in order... |
there is the |
@serundeputy As I'm now focused on |
@BWPanda thanks! totally understandable. Closing as there is no dev bandwidth for this currently; we can re-open or start fresh if dev cycles and priorities change in the future. |
This is another multisite-related issue. Currently, I cannot run
drush dl [MODULE]
from the/modules
folder (in order to make a module globally available to all sites). I get the following:It'd be nice if it downloaded to
/sites/[SITE]/modules
if you ran it from within a site's folders, or defaulted to downloading to/modules
otherwise.I'm not sure if my running the command from outside a site's folder caused the abnormal termination, or if something else caused that which then prevented the download (which might otherwise have worked)...
Marking as a question until I know whether this is a bug report or a feature request.
The text was updated successfully, but these errors were encountered: