[support] Best practice to major site change?

[Ryan LeTulle]

you could use DRUSH to mitigate addtl maintenance overhead when performing
updates etc.

Ryan LeTulle

web www.bayousoft.com
twitter www.twitter.com/bayousoft





On Thu, Sep 16, 2010 at 7:53 AM, Hiroaki Honshuku <madflute at gmail.com>wrote:

>
> Thank you for your response.
> That is a possibility I thought about but I was concerned with maintenance.
>  I would like to avoid double installation if possible.
>
> --
> - Hiro
>
> Hiroaki Honshuku, A-NO-NE Music, Greater Boston
> http://a-no-ne.com   http://anonemusic.com
>
>
>
> On 2010/09/16, at 8:01, Ryan LeTulle wrote:
>
> What operating system/web server?
>
> With Linux/Apache:
>
> I usually create subdomains in dns (i.e. school1.mysite.com,
> school2.mysite.com).  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.
>
> HTH
>
> Ryan LeTulle
>
> web www.bayousoft.com
> twitter www.twitter.com/bayousoft
>
>
>
>
>
> On Thu, Sep 16, 2010 at 12:54 AM, A-NO-NE Music <madflute at anonemusic.com>wrote:
>
>> Drupal 6.19
>> OG6x-1.4
>>
>> Up until this semester, I needed this student portal site for one school
>> only.  Now I need another portal for different school.
>>
>> Before:
>> http://mysite.com
>>
>> Change needed to
>> Login page >
>>        http://mysite.com/school1
>>        http://mysite.com/school2
>>
>> 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.
>>
>>
>> --
>> - Hiro
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20100916/df1651d6/attachment.html