It has been a while Phil! I hope you are doing well. I'm not sure when we introduced this but there is a setting for "Absolute URL to site (if required)" that might be useful to you.
If that is not enough, maybe this trick will help.I run three separate domains on my site: rollerweblogger.org, linusjohnson.com and photophys.com by replacing Roller's index.jsp with this: https://gist.github.com/snoopdave/dc120ae36f63bf4a531c1aa3230bc14a Hope that helps. Cheers, Dave On Wed, Jan 25, 2023 at 7:04 PM Phillip Rhodes <motley.crue....@gmail.com> wrote: > Hello Roller community, long time no see! > > I've been running Roller for quite some time, hosting the blog for Fogbeam > Labs. > > https://www.fogbeam.com/blog > > And it's worked quite fine all this time. So much so that I haven't been > bothered to upgrade, which may play into my question here. Or maybe not. > > Anyway, the goal is to have another blog now, other than the main blog. The > Fogbeam "AI Blog". So I created a new blog, and that works fine if I > reference it by https://www.fogbeam.com/blog/aiblog, as expected. > > The problem is, I'd really like it to be transparently available as > https://aiblog.fogbeam.com. With that in mind, I created the necessary DNS > record, new Apache VirtualHost entry, and used mod_rewrite to rewrite > things so that traffic coming to aiblog.fogbeam.com is proxied to > fogbeam.com/blog/. And that works fine as such. You can hit the URL > https://aiblog.fogbeam.com and the blog loads and everything works. > > The only remaining issue, which admittedly is just a minor annoyance, is > that links generated by Roller like the entry permalink are still generated > using the path that includes http://www.fogbeam.com/blog. For example: > > https://www.fogbeam.com/blog/aiblog/entry/test > > What I had hoped to find in the settings for the child blog was an option > for the absolute URL for the child, but I don't see such a thing. Not sure > offhand if that's because it doesn't exist (and never will?) or if maybe > it's a setting that my copy of Roller is too old to support. Or maybe there > *is* a way to do it and I just can't find it? > > If anybody can offer any advice it would be greatly appreciated. This isn't > a show-stopper by any means, but it's something I'd like to address if > possible. > > And yes, I'll upgrade my Roller install soon, one way or the other. Now > that I have the site build all automated with Ansible, it shouldn't take me > too much work to update my scripts to install the newest version. > > > Thanks! > > > Phil > > > This message optimized for indexing by NSA PRISM >