ian at flash
Mar 11, 2011, 7:42 AM
Post #4 of 6
Actually - skip question 1. I'll point a different name in the domain other than www to Bric, and
Re: Integrating Bricolage with an existing Apache installation
[In reply to]
then use www for the site.
ian [at] flash
Mon - Wed: +31 (0) 629 202752
Thu - Sun: +44 (0) 7815 142001
On 11/03/11 15:06, Ian Gibbs wrote:
> Thanks Greg. That makes sense.
> Two follow-on questions, then:
> (1) I'd like to serve the content using the same vhost as bricolage (using a different one will
> require me to consume another domain name. I see the /login location in the vhost. If I change the
> document root for the vhost to be that for the site, will that break Bric in any way?
> If I take out
> DocumentRoot /usr/local/bricolage/comp
> is that a problem? I can foresee the Perl*Handler directives giving me some problems integrating
> with other perl content on the site. I imagine I would have to replace it with an Alias directive in
> each Location
> (2) What strategies do users have for automatically linking the static content from new stories? If
> a create a new page, I want it to be linked somewhere automatically. I understand that this is where
> we blur the line between blogging and CMS, but I can't imagine the Bric admins everywhere are
> manually linking new pages. It would somewhat ruin the CMS approach.
> Ian Gibbs
> ian [at] flash
> Mon - Wed: +31 (0) 629 202752
> Thu - Sun: +44 (0) 7815 142001
> On 11/03/11 14:17, Greg Heo wrote:
>> Hi Ian,
>> Bricolage is all about managing and publishing the content, not serving it. So you're right, it
>> expects to put the finished files (HTML, PHP, etc.) either locally on the filesystem or on a
>> remote server.
>>> Q: What directory should I be using as the Document Root of the Server in the Destination in
>> If the burner is writing files locally, put in a path (e.g. /usr/local/www/mypublishedsite.com).
>> You can then point an Apache vhost's document root to this same path (see next question)
>>> Q: How am I expecting Apache to know where to find it?
>> The vhost you have set up (with all the Bricolage code in it) is for serving up the CMS itself.
>> You'll need to set up a separate vhost for the "real" public site with all the content Bricolage
>> is churning out.
>> After coming from Wordpress/Movable Type, I remember this being a confusing point when I started
>> with Bricolage. The CMS is its own site and whatever it publishes is its own site.
>> Hope this helps,
>> Greg Heo
>> web and software developer