Posted by bbakelaar on April 1, 2016 at 9:23pm
I guess that says it all about the state of Drupal multisite? Disagree?
Or is there some other location where all the action is happening?
2 posts and 1 comment in the past 6 months
I guess that says it all about the state of Drupal multisite? Disagree?
Or is there some other location where all the action is happening?
Comments
I think multi-site is edge case for Drupal
Especially with the direction of Drupal being more and more for big sites end enterprise level clients, where and with service providers like Pantheon that don't support the functionality.
As such, and since it seems to just work (and has for a very long time), I wouldn't expect a lot of conversation around it. Mostly edge-case multi-site (which is really edge-case). :)
Agreed
Based on my current knowledge, that seems to be true. Do you, or does anyone, know where the "multisite just works" boundaries are defined? :) In other words, what is normal use case, and what is edge case?
Ben Bakelaar
Founder, Human Experience Systems, L.L.C.
Founder, NJ UX Web Design Bootcamp
I do not know where those boundaries are
I just know that what I do works, which I think is mainly a generic use case of one Drupal code base for all sites and each site having its own database and its own sites/domainname.tld directory (mostly for files, but also for custom or site specific modules and themes).
I do know that symlinking the sites directory and/or the domainname.tld directory does not cause any problems. :)