Skip to content
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

Support multisite setups #37

Closed
ghost opened this issue May 17, 2016 · 9 comments · Fixed by #143
Closed

Support multisite setups #37

ghost opened this issue May 17, 2016 · 9 comments · Fixed by #143

Comments

@ghost
Copy link

ghost commented May 17, 2016

When running drush dl devel from /backdrop/sites/[sitename] I get the following message:

Success: Project devel downloaded to /backdrop/modules/devel.

It should download to /backdrop/sites/[sitename]/modules instead.


PR @BWPanda #143

@ghost ghost added the type - bug label May 17, 2016
@serundeputy
Copy link
Member

Thanks for the report @BWPanda!

I have little experience w/ multisite in Drupal and none in Backdrop 😦 So, It'll probably take me a while to get to this and setup a multisite to test against, but this is what I understand needs to happen here:

  1. Check where the user is executing the drush dl command from
    Is it a generic location, or in /backdrop/sites/[sitename] if we are in /backdrop/sites/[sitename] then put the module in /backdrop/sites/[sitename]/modules otherwise proceed as normal.

@ghost
Copy link
Author

ghost commented Jan 17, 2018

Closing this as a duplicate of #15

@ghost ghost closed this as completed Jan 17, 2018
@ghost
Copy link
Author

ghost commented Jan 18, 2018

Nope, sorry, not a duplicate of that issue (got confused).

@ghost ghost reopened this Jan 18, 2018
@ghost
Copy link
Author

ghost commented Jan 18, 2018

This happens with dl and up. Basically this issue is a feature request to support multisite.

@ghost ghost changed the title Drush installs modules to root folder in multisite setup Support multisite setups Jan 18, 2018
@ghost
Copy link
Author

ghost commented Jan 18, 2018

@serundeputy I agree with your idea of what needs to happen to make this work. I'd submit a PR myself, but I'm stuck on the first part: working out how to check where the user is executing the drush command from...

@ghost ghost mentioned this issue Apr 27, 2018
@ghost
Copy link
Author

ghost commented Apr 27, 2018

Added PR that fixes this (with my testing).

@ghost
Copy link
Author

ghost commented Aug 13, 2018

This is working, so closing this issue now...

@ghost ghost closed this as completed Aug 13, 2018
@ghost
Copy link
Author

ghost commented Aug 28, 2018

Oi, this isn't fixed/committed yet, don't know what I was thinking...

@ghost ghost reopened this Aug 28, 2018
@ghost ghost removed the help wanted label Aug 28, 2018
@serundeputy
Copy link
Member

thanks @BWPanda I've merged this and it will ship with 0.3.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants