URL:
<http://gna.org/support/?func=detailitem&item_id=719>
Summary: savannah.conf.pl documentation lack of clarity
(`brother` domains)
Project: Savane
Submitted by: mech
Submitted on: Tue 09/13/2005 at 23:37
Category: Installation/Configuration
Priority: 5 - Normal
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Release:
_______________________________________________________
Details:
# Brother HTTP(s) domain:
# You can run Savannah with two different domain names. You'll be able
# to write a different configuration for each one.
# The two brother/companion sites will share the same database.
# /etc/savannah/savannah.conf.pl is far more important since the
default
# access to the database is done using this one.
# Here you can let your savannah installation aware of the existence
# of a brother/companion site, so while people login, it will be
allowed
# to them to login on both site in one click.
# If you do not have brother/companion site, comment out.
# our $sys_brother_domain="";
Says that you can have two different config files for this main site and the
`brother` site, but doesn`t say where the `brother` site`s config goes, what
it must be called, etc. This is a particularly important `hole` in the
documentation to me, because I do in fact want to run two savanes on the same
system, for two wholly unrelated sets of projects that have their own domain
names (e.g. www.foo.com and savane.foo.com and mailman.foo.com on the one
hand, and www.bar.com, savane.bar.com and mailman.bar.com on the other); 2
virtual hosts on the same machine. I get the strong impression that savane
isn`t really able to handle this without being installed twice in completely
different locations (and I do mean completely, including the config file
directory, which appears to not be readily changeable without using special
environment variables, the documentation for which is inadequate in the
./configure process - it just says that apache has to be told the env var, as
does `the shell` (what shell?), which doesn`t mean anything to a non-expert
user. What I gather from the savannah.conf.pl material on this topic is that
you can set up a virtual host for a secondary, `slave` savane that uses the
same database AND the same users (why??), but uses different homepage
paths/hostnames, etc. I don`t really see the point of making such a
`brother` site, though maybe some do. I`m not saying the feature should be
removed, just better documented as to how to do this (where does the config
file for the brother go?), and that there needs to be a way to use the same
installed savane software to run more than one savane, each with its own
database, users, etc., either on the same vhost or on separate vhosts running
on the same machine. That is: foo.com/savane1 and foo.com/savane2, or
savane1.foo.com and savane2.foo.com.
_______________________________________________________
Reply to this item at:
<http://gna.org/support/?func=detailitem&item_id=719>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
