Vicki,
I use the same Apache binary and launch it twice with two .conf files,
once with the httpd.conf we're used to, and once with the conf files
created by the bric install. If you have mod_perl in your httpd you
should be able to separate and manage your services on one box to your
liking.
Quick thoughts:
1. Upon install I use the 'm' multi option. This way all the
bricolage Perl goodies will be where I can keep an eye on them, and the
bric_apachectl, etc are all where I need them for each install. (And
they'll be that much further away from the apachectl you might be
using). This way I can always back out of any future bricolage
install.
2. I run bric with no virtual host (there are plenty of threads on this
in the Archives), but I make the port number roughly mirror the bric
version. http://fake.com:8132/ http://fake.com:8146/ etc...
3. Bric under heavy use can gobble up resources in a server, so be
careful how much you pile on to one box. I've found that I can run
quite a few static sites and two or three bric installs on a dual PIII
with a GB of RAM and hardware RAID. The problems only come when you
try to do global republishing via SOAP, but recently steps have been
taken to minimize the impact of those operations on the whole box.
4. The only part of the bricolage experience that has two left feet is
not really Bric's fault. But should you decide to upgrade to the
1.5.x series, you'll need to update HTML::Mason. If you are not
running any other perl apps that need Mason, you're fine. If you do
and decide you want to go back to 1.4.6, then you have to downgrade
Mason yourself, which is a minor but important thing.
Good luck!
On Saturday, February 15, 2003, at 01:30 AM, Vicki Brown wrote:
> First -
> I want to try Bricolage. I'd like to play with it., But there is a big
> caveat
> - I don't want Bricolage to control our web services. I don't want it
> in
> control of our Apache httpd.conf file, or our primary server. I don't
> want it
> to get in my way or cause more than a few lines of change to my Apache
> httpd.conf file.
>
> I'm happy to have bric_apachectl start Bricolage, but I don't want
> that same
> command able to start and stop Apache...
>
> I want Apache to remain almost unaltered, and yet be able to start
> (and stop)
> Bricolage alongside Apache and my other VirtualHosts without causing
> noticeable changes to our configuration.
>
> I am beginning to fear this is not possible. I am hoping I am wrong.
>
> If I am wrong, I'm hoping someone can help me get Bricolage working.
>
> If I am not wrong (if Bricolage insists on being in control), please
> let me
> know and everyone can stop reading at this point...
>
> ===============================
>
> Presuming I _can_ get Bricolage to play nice _with_ Apache but not be
> in
> control, I want Bricolage to be implemented as bric.cfcl.com.
> Preferably
> bric.cfcl.com:8080 but I can live with bric.cfcl.com on port 80.
>
> The INSTALL docs says
> To have Bricolage run as the main server process on your Apache
> server, simply add the following two lines to your httpd.conf
> file
> (an example is provided in conf/httpd.conf ):
> PerlPassEnv BRICOLAGE_ROOT
> PerlModule Bric::App::ApacheConfig
>
> This is something I decidedly do not want (and when I tested this by
> putting
> these two lines into httpd.conf, Bricolage tried to override our entire
> Apache configuration). That cannot be allowed, even for a few minutes.
>
> So I tried again. INSTALL also says
> You can also configure Bricolage to run on a virtual host. See
> _Configuration_ below.
>
> Unfortunately, when I looked at the Configuration section, there were
> no
> examples for such a configuration. There is nothing specifically about
> Virtual hosts that I can find in the Configuration section, other than
> VHOST_SERVER_NAME.
>
> I am guessing I do need to edit some number of values in
> /usr/local/bricolage/conf/bricolage.conf
>
> Some questions:
>
> APACHE_CONF = /usr/local/bricolage/conf/httpd.conf
> Given that I _don't want Bricolage "in charge" should I reset this to
> /usr/local/apache/conf/httpd.conf?
>
> LISTEN_PORT = 8080
> for the bric.cfcl.com VirtualHost only, seems OK... at least it tries
> to get
> there
>
> VHOST_SERVER_NAME = bric.cfcl.com
> should be OK...
>
> MANUAL_APACHE =
> I'm afraid that I find the explanation of this flag to be somewhat
> opaque. Do
> I set it to On, set it and leave it, reset it...?
>
> I most definitely want Apache to be configured "manually" by me, in the
> /usr/local/apache/...httpd.conf file.
>
> --------
>
>
> I tried using a standard Apache <VirtualHost> configuration in my
> /usr/local/apache/conf/httpd.conf file:
> Listen 80
> Listen 8080
> ...
> # Canta Forda Computer Laboratory (CantaForda) (top VH is
> default!)
>
> <VirtualHost *:80>
> DocumentRoot /usr/local/Server/WWW/web/cfcl
> ServerAlias *.cantaforda.com cantaforda.com www.cfcl.com
> ServerName cfcl.com
> ...
> </VirtualHost>
> ...
>
>
> # Bricolage server (within CFCL domain)
> <VirtualHost *:8080>
> DocumentRoot /usr/local/bricolage/comp
> ServerName bric.cfcl.com
> </VirtualHost>
>
> and I can reach http://bric.cfcl.com:8080
> The first time this worked I got the login page and it immediately
> disappeared and was replaced by about:blank. Since the reboot and a
> couple
> of *ctl restarts I get an Internal Server error, with this in the
> error_log
>
> [Fri Feb 14 21:59:23 2003] [error] [client 192.168.254.206] Unable to
> connect to database: DBI->connect(dbname=bric) failed: could not
> connect to
> server: No such file or directory at
> /usr/local/lib/perl5/site_perl/5.6.1/Bric/Util/DBI.pm line 1310
>
> In addition, the database rollback failed: Bric::Util::DBI --
> /usr/local/lib/perl5/site_perl/5.6.1/Bric/Util/DBI.pm -- 1314
> Unable to connect to database
>
> DBI->connect(dbname=bric) failed: could not connect to server: No
> such file
> or directory at /usr/local/lib/perl5/site_perl/5.6.1/Bric/Util/DBI.pm
> line
> 1310
>
>
> Stack Trace:
> /usr/local/lib/perl5/site_perl/5.6.1/Bric/Util/DBI.pm - 1314 -
> Bric::Util::Fault::new
> /usr/local/lib/perl5/site_perl/5.6.1/Bric/Util/DBI.pm - 526 -
> Bric::Util::DBI::_connect
> /usr/local/lib/perl5/site_perl/5.6.1/Bric/App/Handler.pm - 243 -
> Bric::Util::DBI::begin
> /usr/local/lib/perl5/site_perl/5.6.1/Bric/App/Handler.pm - 241 - (eval)
> /dev/null - 0 - Bric::App::Handler::handler
> /dev/null - 0 - (eval)
>
>
> [Fri Feb 14 21:59:23 2003] [error] Can't call method "uri" on an
> undefined
> value at /usr/local/bricolage/data/obj/BRIC_UI/errors/500.mc line 31,
> <GEN3>
> line 3.
>
> [Fri Feb 14 21:59:23 2003] [error] [client 192.168.254.206]
> Bric::Util::DBI
> -- /usr/local/lib/perl5/site_perl/5.6.1/Bric/Util/DBI.pm -- 1314
> Unable to connect to database
>
> DBI->connect(dbname=bric) failed: could not connect to server: No
> such file
> or directory at /usr/local/lib/perl5/site_perl/5.6.1/Bric/Util/DBI.pm
> line
> 1310
>
>
> When I added the
> PerlPassEnv BRICOLAGE_ROOT
> PerlModule Bric::App::ApacheConfig
> back, I get a "Forbidden" error at bric.cfcl.com:8080
>
> Every time I experiment I run the risk of breaking our web services
> again and
> this causes domestic upset. I am loathe to continue frobbing the
> configuration until I have a better view of what might be in store.
>
> Feeling hopelessly confused. Hoping someone has done this before...
> --
> - Vicki
>
> Vicki Brown ZZZ Journeyman Sourceror:
> P.O. Box 1269 zz |\ _,,,---,,_ Scripts & Philtres
> San Bruno, CA zz /,`.-'`' -. ;-;;,_ Perl, Unix, MacOS
> 94066 USA |,4- ) )-,_. ,\ ( `'-'
> mailto:vlb@cfcl.com '---''(_/--' `-'\_) http://www.cfcl.com/~vlb
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by: FREE SSL Guide from Thawte
> are you planning your Web Server Security? Click here to get a FREE
> Thawte SSL guide and find the answers to all your SSL security issues.
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
> _______________________________________________
> Bricolage-General mailing list
> Bricolage-General@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bricolage-general
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bricolage-General mailing list
Bricolage-General@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bricolage-general
I use the same Apache binary and launch it twice with two .conf files,
once with the httpd.conf we're used to, and once with the conf files
created by the bric install. If you have mod_perl in your httpd you
should be able to separate and manage your services on one box to your
liking.
Quick thoughts:
1. Upon install I use the 'm' multi option. This way all the
bricolage Perl goodies will be where I can keep an eye on them, and the
bric_apachectl, etc are all where I need them for each install. (And
they'll be that much further away from the apachectl you might be
using). This way I can always back out of any future bricolage
install.
2. I run bric with no virtual host (there are plenty of threads on this
in the Archives), but I make the port number roughly mirror the bric
version. http://fake.com:8132/ http://fake.com:8146/ etc...
3. Bric under heavy use can gobble up resources in a server, so be
careful how much you pile on to one box. I've found that I can run
quite a few static sites and two or three bric installs on a dual PIII
with a GB of RAM and hardware RAID. The problems only come when you
try to do global republishing via SOAP, but recently steps have been
taken to minimize the impact of those operations on the whole box.
4. The only part of the bricolage experience that has two left feet is
not really Bric's fault. But should you decide to upgrade to the
1.5.x series, you'll need to update HTML::Mason. If you are not
running any other perl apps that need Mason, you're fine. If you do
and decide you want to go back to 1.4.6, then you have to downgrade
Mason yourself, which is a minor but important thing.
Good luck!
On Saturday, February 15, 2003, at 01:30 AM, Vicki Brown wrote:
> First -
> I want to try Bricolage. I'd like to play with it., But there is a big
> caveat
> - I don't want Bricolage to control our web services. I don't want it
> in
> control of our Apache httpd.conf file, or our primary server. I don't
> want it
> to get in my way or cause more than a few lines of change to my Apache
> httpd.conf file.
>
> I'm happy to have bric_apachectl start Bricolage, but I don't want
> that same
> command able to start and stop Apache...
>
> I want Apache to remain almost unaltered, and yet be able to start
> (and stop)
> Bricolage alongside Apache and my other VirtualHosts without causing
> noticeable changes to our configuration.
>
> I am beginning to fear this is not possible. I am hoping I am wrong.
>
> If I am wrong, I'm hoping someone can help me get Bricolage working.
>
> If I am not wrong (if Bricolage insists on being in control), please
> let me
> know and everyone can stop reading at this point...
>
> ===============================
>
> Presuming I _can_ get Bricolage to play nice _with_ Apache but not be
> in
> control, I want Bricolage to be implemented as bric.cfcl.com.
> Preferably
> bric.cfcl.com:8080 but I can live with bric.cfcl.com on port 80.
>
> The INSTALL docs says
> To have Bricolage run as the main server process on your Apache
> server, simply add the following two lines to your httpd.conf
> file
> (an example is provided in conf/httpd.conf ):
> PerlPassEnv BRICOLAGE_ROOT
> PerlModule Bric::App::ApacheConfig
>
> This is something I decidedly do not want (and when I tested this by
> putting
> these two lines into httpd.conf, Bricolage tried to override our entire
> Apache configuration). That cannot be allowed, even for a few minutes.
>
> So I tried again. INSTALL also says
> You can also configure Bricolage to run on a virtual host. See
> _Configuration_ below.
>
> Unfortunately, when I looked at the Configuration section, there were
> no
> examples for such a configuration. There is nothing specifically about
> Virtual hosts that I can find in the Configuration section, other than
> VHOST_SERVER_NAME.
>
> I am guessing I do need to edit some number of values in
> /usr/local/bricolage/conf/bricolage.conf
>
> Some questions:
>
> APACHE_CONF = /usr/local/bricolage/conf/httpd.conf
> Given that I _don't want Bricolage "in charge" should I reset this to
> /usr/local/apache/conf/httpd.conf?
>
> LISTEN_PORT = 8080
> for the bric.cfcl.com VirtualHost only, seems OK... at least it tries
> to get
> there
>
> VHOST_SERVER_NAME = bric.cfcl.com
> should be OK...
>
> MANUAL_APACHE =
> I'm afraid that I find the explanation of this flag to be somewhat
> opaque. Do
> I set it to On, set it and leave it, reset it...?
>
> I most definitely want Apache to be configured "manually" by me, in the
> /usr/local/apache/...httpd.conf file.
>
> --------
>
>
> I tried using a standard Apache <VirtualHost> configuration in my
> /usr/local/apache/conf/httpd.conf file:
> Listen 80
> Listen 8080
> ...
> # Canta Forda Computer Laboratory (CantaForda) (top VH is
> default!)
>
> <VirtualHost *:80>
> DocumentRoot /usr/local/Server/WWW/web/cfcl
> ServerAlias *.cantaforda.com cantaforda.com www.cfcl.com
> ServerName cfcl.com
> ...
> </VirtualHost>
> ...
>
>
> # Bricolage server (within CFCL domain)
> <VirtualHost *:8080>
> DocumentRoot /usr/local/bricolage/comp
> ServerName bric.cfcl.com
> </VirtualHost>
>
> and I can reach http://bric.cfcl.com:8080
> The first time this worked I got the login page and it immediately
> disappeared and was replaced by about:blank. Since the reboot and a
> couple
> of *ctl restarts I get an Internal Server error, with this in the
> error_log
>
> [Fri Feb 14 21:59:23 2003] [error] [client 192.168.254.206] Unable to
> connect to database: DBI->connect(dbname=bric) failed: could not
> connect to
> server: No such file or directory at
> /usr/local/lib/perl5/site_perl/5.6.1/Bric/Util/DBI.pm line 1310
>
> In addition, the database rollback failed: Bric::Util::DBI --
> /usr/local/lib/perl5/site_perl/5.6.1/Bric/Util/DBI.pm -- 1314
> Unable to connect to database
>
> DBI->connect(dbname=bric) failed: could not connect to server: No
> such file
> or directory at /usr/local/lib/perl5/site_perl/5.6.1/Bric/Util/DBI.pm
> line
> 1310
>
>
> Stack Trace:
> /usr/local/lib/perl5/site_perl/5.6.1/Bric/Util/DBI.pm - 1314 -
> Bric::Util::Fault::new
> /usr/local/lib/perl5/site_perl/5.6.1/Bric/Util/DBI.pm - 526 -
> Bric::Util::DBI::_connect
> /usr/local/lib/perl5/site_perl/5.6.1/Bric/App/Handler.pm - 243 -
> Bric::Util::DBI::begin
> /usr/local/lib/perl5/site_perl/5.6.1/Bric/App/Handler.pm - 241 - (eval)
> /dev/null - 0 - Bric::App::Handler::handler
> /dev/null - 0 - (eval)
>
>
> [Fri Feb 14 21:59:23 2003] [error] Can't call method "uri" on an
> undefined
> value at /usr/local/bricolage/data/obj/BRIC_UI/errors/500.mc line 31,
> <GEN3>
> line 3.
>
> [Fri Feb 14 21:59:23 2003] [error] [client 192.168.254.206]
> Bric::Util::DBI
> -- /usr/local/lib/perl5/site_perl/5.6.1/Bric/Util/DBI.pm -- 1314
> Unable to connect to database
>
> DBI->connect(dbname=bric) failed: could not connect to server: No
> such file
> or directory at /usr/local/lib/perl5/site_perl/5.6.1/Bric/Util/DBI.pm
> line
> 1310
>
>
> When I added the
> PerlPassEnv BRICOLAGE_ROOT
> PerlModule Bric::App::ApacheConfig
> back, I get a "Forbidden" error at bric.cfcl.com:8080
>
> Every time I experiment I run the risk of breaking our web services
> again and
> this causes domestic upset. I am loathe to continue frobbing the
> configuration until I have a better view of what might be in store.
>
> Feeling hopelessly confused. Hoping someone has done this before...
> --
> - Vicki
>
> Vicki Brown ZZZ Journeyman Sourceror:
> P.O. Box 1269 zz |\ _,,,---,,_ Scripts & Philtres
> San Bruno, CA zz /,`.-'`' -. ;-;;,_ Perl, Unix, MacOS
> 94066 USA |,4- ) )-,_. ,\ ( `'-'
> mailto:vlb@cfcl.com '---''(_/--' `-'\_) http://www.cfcl.com/~vlb
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by: FREE SSL Guide from Thawte
> are you planning your Web Server Security? Click here to get a FREE
> Thawte SSL guide and find the answers to all your SSL security issues.
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
> _______________________________________________
> Bricolage-General mailing list
> Bricolage-General@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bricolage-general
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bricolage-General mailing list
Bricolage-General@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bricolage-general