> One option for a hosting company is to run their own core Drupal system,<br>> with each customer being able to edit the contents of a subdirectory in the<br>> sites/ directory. That way they can keep control over much of the behaviour,
<br>> keep it patched, remove CPU-hungry bits at their own discretion etc. I've<br>> not heard of anyone doing this yet, though.<br><br>In fact this is the basic technology behind Bryght's open source hostmaster platform, and we've done this a lot for different customers.
<br><br>However, it's not a performance benefit, it's a maintainability benefit (in theory). You don't get less of a footprint in Apache because you share the underlying files.<br><br>For shared hosts, there's no real benefit for them as they're not doing large enough scale systems to bother, plus most of them don't touch code (and wouldn't know Drupal from wordpress without grepping for it).
<br><br>Best,<br><br>JL<br><br><div><span class="gmail_quote">On 7/10/07, <b class="gmail_sendername">Khalid Baheyeldin</b> <<a href="mailto:kb@2bits.com">kb@2bits.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><span class="e" id="q_113b08f43400461e_0">On 7/10/07, <b class="gmail_sendername">Lennart Borgman (gmail)</b> <<a href="mailto:lennart.borgman@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
lennart.borgman@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
J-P Stacey wrote:<br>> One option for a hosting company is to run their own core Drupal system,<br>> with each customer being able to edit the contents of a subdirectory in<br>> the sites/ directory. That way they can keep control over much of the
<br>> behaviour, keep it patched, remove CPU-hungry bits at their own<br>> discretion etc. I've not heard of anyone doing this yet, though.<br><br>Thanks J-P.<br><br>I have always wondered why an installation like that is not the standard
<br>for shared web hosts. A problem is perhaps incompatibilities at when<br>upgrading, but that could be solved by having the customer specific part<br>pointing to a special location. When the web host upgrades Drupal (and
<br>other similar software) they could just do a fresh install in a new<br>location.<br><br>At the web host I am currently using they do not handle Drupal,<br>WordPress etc that way (which surprised me a lot when I first saw it).
<br>Does Drupal have builtin support for this installation structure?<br><br></blockquote></div><br></span></div>Specialized hosts (e.g. Bryght) does that already (have their own repository<br>
and sanctioned modules.<br clear="all"><br>However, most shared web hosts are small operations, or simply not into <br>maintaining code of any kind. They are motel operators, not caterers, builders,<br>or engineers. If they do this for Drupal, they have to do it for 100 other things
<br>their customers ask for. <br><br>This is why there are things like Fantastico, which provides this feature for web <br>hosts, and they subscribe to it and give it to their customers as a feature.<br><br>So, don't expect any shared host to do this any time soon.
<div><span class="e" id="q_113b08f43400461e_2"><br>-- <br><a href="http://2bits.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">2bits.com</a><br><a href="http://2bits.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://2bits.com</a><br>Drupal development, customization and consulting.
</span></div></blockquote></div><br><br clear="all"><br>-- <br>Jonathan Lambert<br>Principal & CEO<br>Email: <a href="mailto:j@workhabit.com">j@workhabit.com</a><br>Phone: 415-376-7274<br><br>WorkHabit, Inc. (Formerly FireBright, Inc.)
<br><a href="http://www.workhabit.com/">http://www.workhabit.com/</a><br><a href="http://www.workhabit.org/">http://www.workhabit.org/</a>