-
Notifications
You must be signed in to change notification settings - Fork 22
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
Issue #12: Provide full support for multisites. #37
Conversation
Nice work! But I do have one concern. Currently Both doesn't seem perfect to me. If I use multisite, I always share at least the majority of contrib modules (hence main dir is fine). Only single modules and likely the theme or some layouts are site specific. |
@indigoxela Thanks for the feedback! It's good to hear how other people use Backdrop/multisite. So with this PR if you run I believe this is how Drush for Drupal 7 works. Drush for Backdrop doesn't fully support multisites yet, which is why I started using How would you prefer it to work? E.g. where do you prefer to run commands from, and where do you want them to download to? |
BTW @indigoxela, are you on Gitter? https://gitter.im/backdrop/backdrop-issues If so, we can chat there if it's easier. |
Ah, I didn't test that from the backdrop root, as "b" says "BackdropCMS is not installed yet." - but downloads it then to the main dirs. Cool, very helpful! The warning message was misleading me. BTW: Drush with D7 allows downloading projects to anywhere, regardless of an install. |
Yeah, that message is displayed if |
Fixes #12