Here are some pages with info about multi-domain sites:

What's new in Roller 5.0
   https://cwiki.apache.org/confluence/x/bgE7AQ
   http://www.slideshare.net/snoopdave/whats-new-in-roller5

Proposal for simple multi-domain
   https://cwiki.apache.org/confluence/x/vScB

The JIRA issue for simple multi-domain
   https://issues.apache.org/jira/browse/ROL-1670

Hope that helps...

- Dave


On Sep 30, 2010, at 3:03 AM, Christopher Dodunski wrote:

> Hi All,
> 
> I understand Apache Roller is soliciting volunteers to assist with the
> likes of documentation.  I have a proposal that may be of mutual benefit.
> 
> Existing documentation doesn't appear to explain the 'multiple domain'
> functionality of Roller 5.  If someone here is gracious enough to assist
> me with configuring httpd/mod_proxy/tomcat/roller to host multiple domains
> (see below), I will document the process.  Along with screenshots, this
> could then perhaps form part of the Roller 5 documentation which,
> presently, seems not to deal with this one vital topic.
> 
> We would dearly like to add weblogging to the list of features offered to
> clients whose websites we host.  Savvy clients, though, expect to have
> URLs of the form blog.their-domain.com.  Of course this is easily achieved
> with Wordpress - multiple instances of.  But this quickly becomes
> unwieldy, consuming more and more disk space.
> 
> Hoping Roller 5 is the answer.
> 
> Regards,
> 
> Chris Dodunski.
> 
> 
>> Hi Dave,
>> 
>> Thank you for your reply.  I took the plunge, and installed Roller 5 RC2.
>> It is the multiple domain URL feature that most interests me - starting
>> off with six.  But I have had only partial success.  So here is how one of
>> the six was configured.
>> 
>> 1) Created a weblog with a handle of "christopher".  Confirmed as working
>> fine under the URL http://www.optomus.com:8080/roller/christopher
>> 
>> 2) Configured a subdomain on my DNS - http://blog.christopher.net.nz
>> 
>> 3) Established an Apache virtual host for this URL, and set the following
>> mod_proxy directives:
>> 
>>    ProxyPass / ajp://127.0.0.1:8009/roller/christopher/
>>    ProxyPassReverse / ajp://127.0.0.1:8009/roller/christopher/
>> 
>> 4) Added the following directive to roller-custom.properties:
>> 
>>    weblog.absoluteurl.christopher=http://blog.christopher.net.nz
>> 
>> 5) Restarted Apache and Tomcat.
>> 
>> If you browse to http://blog.christopher.net.nz you will see what I mean
>> by partial success.  The correct weblog loads, but the CSS hasn't loaded,
>> and the links don't work.  I'm guessing my configuration isn't right, as
>> you are successfully operating several domain URLs from a single instance
>> of Roller, yes?
>> 
>> Looking forward to finding a solution.
>> 
>> Thanks & regards,
>> 
>> Chris.
>> 
>> 
>>> Hi Chris,
>>> 
>>> Roller 5.0 is basically ready for release and we are at the stage of
>>> making "release candidates" available for testing and then fixing bugs
>>> and problems that people encounter. These candidates are not supposed
>>> to be used in production, but I'm running my site on one right now. I
>>> would guess that we'll go through 2-3 more RCs and do the official
>>> release sometime in the next 2 months, but that is just a guess.
>>> 
>>> Custom themes are stored in the database and that database upgrade
>>> will take care of migrating them.
>>> 
>>> Obligatory warning: If you do try an RC, make sure you backup
>>> everything including your database.
>>> 
>>> Thanks,
>>> Dave
>>> 
>>> 
>>> On Sat, Sep 25, 2010 at 6:04 AM, Christopher Dodunski
>>> <chrisfromsquir...@christopher.net.nz> wrote:
>>>> Hi,
>>>> 
>>>> I'm currently running Roller 4.
>>>> 
>>>> I'm wondering if anyone here had an idea as to when Roller 5.0 might be
>>>> officially released.  If it is likely to be a fair way off, and release
>>>> candidate 2 is generally considered stable, I might upgrade now rather
>>>> than wait.
>>>> 
>>>> Also, are custom themes stored in the database, or do I have to migrate
>>>> templates/stylesheets across?
>>>> 
>>>> Thanks & regards,
>>>> 
>>>> Chris.
>>>> 
>>>> 
>>> 
>> 
>> 
> 
> 

Reply via email to