Marc G. Fournier said:
>> It does need a seperate VM because of all the Perl stuff and the static
>> mod_perl in Apache.
>
> That's doable with the current VM as well, as mod_perl is already
> installed ... the only issue that I could see is the port 80 that Steve
> mentioned ...
It can be set up to run on a port other than 80 -- that's what I'm doing on my
server.
You might want to try setting it up on a different computer first, though, for
the experience -- when I tried to set it up on mine (I was attempting to do a
virtual host on the same port), I accidentally caused Bricolage to answer all
queries for all virtual hosts, and if my sites had higher traffic, people
might have noticed. :-)
Also, be ready to install a LOT of Perl modules.
The main issue to consider with Bricolage are the memory requirements -- I
think the docs say that it takes something like 25MB per Apache child.
Looking at my server, I see one child at 30MB. So be sure that there's plenty
of RAM available.
> If we are all in agreement that this is the direction we want to go, then
> I can get the VM for this setup tomorrow ... who will/should be given
> "root" to that VM? Elein? Steve? Josh? Let me know ...
The only people who should need direct access to the machine are the people
who will be maintaining any technical aspects of it. All content and
template/layout development and publishing (except deleting files once they're
published) can be done through the interface.
I'd be fine with being the (or one of the) main people doing technical
maintenance on this server, but I wouldn't want to be the only one. I could
help get someone else up to speed, though, if that would help. (Elein?)
Hope this helps,
Steve Simms
Database Developer & Administrator
Medical Media Systems, Inc.
