development question

[Steven Lembark <le...@wrkhors.com>]

apache 1.3.14.

 havemultiple developers hacking html, mod_perl w/ own sandboxes.
need them to start up their own servers on various ports (e.g.,
8081, 8082...).  we are using CVS and need to share access to a
valid httpd.conf file.  

hmmm...  we all use the same httpd.conf and we all step on one 
another w/ ports and dir's.  not good.

no way i know of use specify htdocs as a relative path or use
$HOME or $SANDBOX to set it.

virtual hosts don't work well since everyone collides on the 
main server's PORT setting and none of has have SU access to 
suck up port 80 (which still wouldn't help if we collide on 80).

trying to avoid people using -d for now -- still doesn't help
since DocumentRoot wants an absolute path.

include doesn't work since we are sharing the same CVS tree and
would end up with the same includes -- unless there is something
like

	Include "$ENV{LOGNAME}-conf"

to allow per-user portions of the config.

never learned how to configure apache w/ the perl format,
which might solve the entire thing via $ENV{HOME}.  might not...

so...

anyone have an example httpd.conf (stock or perly) that would
allow multiple people on the same machine to check out the same
httpd.conf, start up httpd w/ -f ./httpd.conf and not collide
on the ports, dir's?   

the only thing i can come up with so far is rather messy,
using, with

	<IfDefine blah>
		Include blah-config
	</IfDefine>

we can edit the common httpd.conf file for each of ourselves.

seems like performing the replacement in-place (e.g., via 
$LOGNAME) would be a cleaner way.

thanx




-- 
 Steven Lembark                                   2930 W. Palmer St.
                                                 Chicago, IL  60647
 lembark@wrkhors.com                                   800-762-1582

Re: development question

[Ken Williams <ke...@forum.swarthmore.edu>]

lembark@wrkhors.com (Steven Lembark) wrote:
>include doesn't work since we are sharing the same CVS tree and
>would end up with the same includes -- unless there is something
>like
>
>	Include "$ENV{LOGNAME}-conf"
>
>to allow per-user portions of the config.

I'd be inclined to do it the other way around.  Start the server using
/blah/blah/httpd -f /home/ralph/myhttpd.conf , then include the central
shared httpd.conf.


  -------------------                            -------------------
  Ken Williams                             Last Bastion of Euclidity
  ken@forum.swarthmore.edu                            The Math Forum