Mailing List Archive

You can use virtual hosts, yes. Just make sure that the SSL_PORT and
LISTEN_PORT directives point to different ports than your content
serving virtual host will be listening on. You'll likely need to use
the MANUAL_APACHE configuration, too, and create your own httpd.conf
file. Michael Robinton can actually supply more information on this
than I can (You listening, Mike?).

If you're just starting out and trying to get a feel for Bricolage,
it's easiest to run it on a separate machine and get to know it there.
That will let you get up to speed learning how to use Bricolage, and
then you can reconfigure it later.

HTH,

David

On Friday, January 3, 2003, at 03:07 PM, Harrison, George (FSH) wrote:

> This seems to imply that virtual hosts are not enough to get Apache to
> respond to a request for content from a browser. Is this correct? Or
> am I
> missing something?
>
> Thanks
>
> gh
>
> David Wheeler wrote:
>
>>> is it expected that I will create virtual server in bricolage http
>>> config file (if so is there a directory within bricolage install that
>>> should/could be used as a default or should it be outside of
>>> bricolage
>>> install)? or that I will run separate apache installation (on same or
>>> different machine)? or any of that? how do I tell bricolage how to
>>> publish the stuff to particular location? I guess it can use either
>>> ftp or file copy but I can't find out how to specify either in
>>> publish
>>> part of admin (bricolage workspace page).
>>
>>
>> You need to run a separate Apache process. It can be on a separate
>> machine (recommended for production environments) or the same machine
>> (when it's best to use SSL_PORT and LISTEN_PORT directives to separate
>> Bricolage httpds from your other httpds [this needs better
>> documentation, too]).
>>
>> You use destinations to "tell Bricolage how to publish to a particular
>> location." You have to specify ftp or copy in the destination profile
>> by
>> adding a "Move" action.
>>
>> HTH,
>
>
> -------------------------------------------------------
> 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
>
>
--
David Wheeler AIM: dwTheory
david@wheeler.net ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: Theory@jabber.org



-------------------------------------------------------
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

Harrison, George (FSH) wrote:
> This seems to imply that virtual hosts are not enough to get Apache to
> respond to a request for content from a browser. Is this correct? Or am I
> missing something?

it is enough, either virtual host directly in the bricolage
httpd.conf like this:

# erik: virtual host, this is where the content is visible
<VirtualHost 207.214.70.22:80>
<IfModule mod_dir.c>
DirectoryIndex index.html index.htm index.shtml index.cgi index.php
</IfModule>

DocumentRoot /var/wwwBricolage
ServerName billteam.snrmca.pbi.net
</VirtualHost>

or completely separate apache installation, either on same machine
(using, of course, different port(s)) or different machine.

erik

>
> Thanks
>
> gh
>
> David Wheeler wrote:
>
>
>>> is it expected that I will create virtual server in bricolage http
>>>config file (if so is there a directory within bricolage install that
>>>should/could be used as a default or should it be outside of bricolage
>>>install)? or that I will run separate apache installation (on same or
>>>different machine)? or any of that? how do I tell bricolage how to
>>>publish the stuff to particular location? I guess it can use either
>>>ftp or file copy but I can't find out how to specify either in publish
>>>part of admin (bricolage workspace page).
>>
>>
>>You need to run a separate Apache process. It can be on a separate
>>machine (recommended for production environments) or the same machine
>>(when it's best to use SSL_PORT and LISTEN_PORT directives to separate
>>Bricolage httpds from your other httpds [this needs better
>>documentation, too]).
>>
>>You use destinations to "tell Bricolage how to publish to a particular
>>location." You have to specify ftp or copy in the destination profile by
>>adding a "Move" action.
>>
>>HTH,
>
>
>
> -------------------------------------------------------
> 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
>




-------------------------------------------------------
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

> You can use virtual hosts, yes. Just make sure that the SSL_PORT and
> LISTEN_PORT directives point to different ports than your content
> serving virtual host will be listening on. You'll likely need to use
> the MANUAL_APACHE configuration, too, and create your own httpd.conf
> file. Michael Robinton can actually supply more information on this
> than I can (You listening, Mike?).

Yep, but I wasn't following the thread.... sorry?

What is it that you need to do??
Michael@Insulin-Pumpers.org


-------------------------------------------------------
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

If you are running a virtual host on the same machine as Bricolage, could
you send me your httpd.conf file.

When we set up virtual hosts, apache responds but bricolage won't start. I'm
hoping an example of a working setup will show where we've gone wrong.

If this is not possible, thanks anyway.

gh

> -----Original Message-----
> From: Erik Steffl [mailto:steffl@bigfoot.com]
>
>

> it is enough, either virtual host directly in the bricolage
> httpd.conf like this:
>
> # erik: virtual host, this is where the content is visible
> <VirtualHost 207.214.70.22:80>
> <IfModule mod_dir.c>
> DirectoryIndex index.html index.htm index.shtml
> index.cgi index.php
> </IfModule>
>
> DocumentRoot /var/wwwBricolage
> ServerName billteam.snrmca.pbi.net
> </VirtualHost>
>
>
>
> erik
>
> >
> > Thanks
> >
> > gh
> >
> > David Wheeler wrote:
> >
> >
> >>> is it expected that I will create virtual server in
> bricolage http
> >>>config file (if so is there a directory within bricolage
> install that
> >>>should/could be used as a default or should it be outside
> of bricolage
> >>>install)? or that I will run separate apache installation
> (on same or
> >>>different machine)? or any of that? how do I tell bricolage how to
> >>>publish the stuff to particular location? I guess it can
> use either
> >>>ftp or file copy but I can't find out how to specify
> either in publish
> >>>part of admin (bricolage workspace page).
> >>
> >>
> >>You need to run a separate Apache process. It can be on a separate
> >>machine (recommended for production environments) or the
> same machine
> >>(when it's best to use SSL_PORT and LISTEN_PORT directives
> to separate
> >>Bricolage httpds from your other httpds [this needs better
> >>documentation, too]).
> >>
> >>You use destinations to "tell Bricolage how to publish to a
> particular
> >>location." You have to specify ftp or copy in the
> destination profile by
> >>adding a "Move" action.
> >>
> >>HTH,
> >
> >
> >
> > -------------------------------------------------------
> > 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
> >
>
>
>
>
> -------------------------------------------------------
> 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
>


-------------------------------------------------------
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

> If you are running a virtual host on the same machine as Bricolage,
> could you send me your httpd.conf file.

It's not necessarily desirable to serve content from the host that
runs bricolage. Bricolage is a heavy proces where the parent and each
child process may consume anywhere from 20 to 50 megs each. Running a
virtual host just to serve content carries this overhead as well. If
you have 5 - 10 of these as is typical for a normal apache daemon
burns a lot of resources on the server. A better way to do this is to
run a separate process just for Bric with just a couple of children
and a low maximum child count. I've included my pre-1.4 config files
which should be fine for 1.4/1.5

Note that I'm using apache-ssl, but they should work just as well for
mod-ssl.

Michael

### bricolage.conf
APACHE_BIN = /usr/local/apache/bin/httpsd
APACHE_CONF = /usr/local/bricolage/conf/httpd.conf
LISTEN_PORT = 81
SSL_PORT = 444
ALWAYS_USE_SSL = Off
SSL_ENABLE = apache_ssl
SSL_CERTIFICATE_KEY_FILE = /usr/local/ssl/private/secret.key
SSL_CERTIFICATE_FILE = /usr/local/ssl/certs/cert.crt
NAME_VHOST = *
VHOST_SERVER_NAME = _default_
TEMP_DIR = /usr/local/bricolage/tmp
MANUAL_APACHE = Off
SYS_USER = web
SYS_GROUP = users
DB_NAME = bricdb
DBI_USER = bricx
DBI_PASS = xcirb
MASON_COMP_ROOT = /usr/local/bricolage/comp
MASON_DATA_ROOT = /usr/local/bricolage/data
BURN_ROOT = /usr/local/bricolage/data/burn
INCLUDE_XML_WRITER = No
AUTH_TTL = 28800 # Seconds.
AUTH_SECRET = removed
CHAR_SET = ISO-8859-1
LOGIN_LENGTH = 6
PASSWD_LENGTH = 6
ENABLE_DIST = 1
DIST_ATTEMPTS = 3
PREVIEW_LOCAL = 1
PREVIEW_MASON = 0
DEF_MEDIA_TYPE = text/html
ENABLE_SFTP_MOVER = Off
ALERT_FROM = webmaster@someserver.foo.com
ALERT_TO_METH = bcc # Can also be 'to'
CHECK_PROCESS_SIZE = Off
MAX_PROCESS_SIZE = 56000
CHECK_FREQUENCY = 1
MIN_SHARE_SIZE = 0
MAX_UNSHARED_SIZE = 0
FULL_SEARCH = Off
DEFAULT_FILENAME = index
DEFAULT_FILE_EXT = html
ENABLE_FTP_SERVER = Off

### httpd.conf
ServerType standalone
ServerName rambo
ServerRoot /usr/local/apache
ServerAdmin root@localhost
ServerSignature Email
PidFile /usr/local/bricolage/log/httpd.pid
DocumentRoot /usr/local/bricolage/comp
Listen 81
User web
Group users
KeepAlive Off
MaxKeepAliveRequests 100
KeepAliveTimeout 15
MinSpareServers 2
MaxSpareServers 6
StartServers 2
MaxClients 150
MaxRequestsPerChild 0
ErrorLog /usr/local/bricolage/log/error_log
LogLevel info
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\"
\"%{User-Agent}i\" \"%{Cookie}i\" \"%v:%p\"" combined CustomLog
/usr/local/bricolage/log/access_log combined TypesConfig
/usr/local/apache/conf/mime.types UseCanonicalName On
HostNameLookups Off Timeout 30

#############################################################################
# Use this section if SSL_ENABLE is on in bricolage.conf.
#############################################################################
<ifModule mod_ssl.c>
Listen 444
# Enabled on a per virtual host basis
SSLEngine off
SSLPassPhraseDialog builtin
SSLSessionCache dbm:/usr/local/apache/logs/ssl_scache
SSLSessionCacheTimeout 300
SSLMutex file:/usr/local/apache/logs/ssl_mutex
SSLLog /usr/local/apache/logs/ssl_engine_log
SSLLogLevel info
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
SSLCipherSuite
ALL:!ADH:!EXP56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
</IfModule>
<IfModule apache_ssl.c>
# Platform dependent, but shown for Linux
# SSLRandomFile /dev/random/1024
# SSLRandomFilePerConnection /dev/random 1024
SSLRandomFile /dev/urandom 1024
SSLRandomFilePerConnection /dev/urandom 1024
Listen 444
# Enabled on a per virtual host basis
SSLDisable
SSLCacheServerPath /usr/local/apache/bin/gcache
SSLCacheServerPort /usr/local/bricolage/log/gcache_port
SSLCacheServerRunDir /tmp
SSLSessionCacheTimeout 3600
# SSLRequired Ciphers RC4-MD5:RC4-SHA:IDEA-CBC-MD5:DES-CBC3-SHA
</IfModule>

#############################################################################
# This is where Bricolage actually gets configured.
#############################################################################
PerlPassEnv BRICOLAGE_ROOT
PerlModule Bric::App::ApacheConfig


-------------------------------------------------------
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