you could use DRUSH to mitigate addtl maintenance overhead when performing updates etc.<div><br clear="all">Ryan LeTulle<br><br>web <a href="http://www.bayousoft.com" target="_blank">www.bayousoft.com</a><br>twitter <a href="http://www.twitter.com/bayousoft" target="_blank">www.twitter.com/bayousoft</a><br>
<br><br><br>
<br><br><div class="gmail_quote">On Thu, Sep 16, 2010 at 7:53 AM, Hiroaki Honshuku <span dir="ltr"><<a href="mailto:madflute@gmail.com">madflute@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word"><div><br></div><div>Thank you for your response.</div><div>That is a possibility I thought about but I was concerned with maintenance. I would like to avoid double installation if possible.</div>
<div class="im"><div><br></div><div><div style="font-size:12px">--<br>- Hiro</div><div style="font-size:12px"><br></div><div style="font-size:12px">Hiroaki Honshuku, A-NO-NE Music, Greater Boston</div><div style="font-size:12px">
<a href="http://a-no-ne.com" target="_blank">http://a-no-ne.com</a> <a href="http://anonemusic.com" target="_blank">http://anonemusic.com</a></div></div><div style="font-size:12px"><br></div><div style="font-size:12px">
<br></div><br></div><div class="im"><div><div>On 2010/09/16, at 8:01, Ryan LeTulle wrote:</div><br><blockquote type="cite">What operating system/web server?<br><br>With Linux/Apache:<br><br>I usually create subdomains in dns (i.e. <a href="http://school1.mysite.com/" target="_blank">school1.mysite.com</a>, <a href="http://school2.mysite.com/" target="_blank">school2.mysite.com</a>). Then I create virtual hosts in Apache. Point the old domain into your existing folder and the new domain into a new folder where you will install Drupal again.<br>
<br>HTH<br> <br clear="all">Ryan LeTulle<br><br>web <a href="http://www.bayousoft.com/" target="_blank">www.bayousoft.com</a><br>twitter <a href="http://www.twitter.com/bayousoft" target="_blank">www.twitter.com/bayousoft</a><br>
<br><br><br>
<br><br><div class="gmail_quote">On Thu, Sep 16, 2010 at 12:54 AM, A-NO-NE Music <span dir="ltr"><<a href="mailto:madflute@anonemusic.com" target="_blank">madflute@anonemusic.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left-width:1px;border-left-style:solid;border-left-color:rgb(204, 204, 204);margin-top:0pt;margin-right:0pt;margin-bottom:0pt;margin-left:0.8ex;padding-left:1ex">
Drupal 6.19<br>
OG6x-1.4<br>
<br>
Up until this semester, I needed this student portal site for one school only. Now I need another portal for different school.<br>
<br>
Before:<br>
<a href="http://mysite.com/" target="_blank">http://mysite.com</a><br>
<br>
Change needed to<br>
Login page ><br>
<a href="http://mysite.com/school1" target="_blank">http://mysite.com/school1</a><br>
<a href="http://mysite.com/school2" target="_blank">http://mysite.com/school2</a><br>
<br>
They don't need to share anything but the server space and the domain name. What would be the best practice for this situation? While school2 is still blank, I have too many things under school1 including menus. It won't be practical to modify them one by one, and seeking for a better solution.<br>
<br>
<br>
--<br>
- Hiro</blockquote></div></blockquote></div><div>
</div>
<br></div></div></blockquote></div><br></div>