Re: Team development on mod

Everybody running their own lightweight copy of Apache on separate ports would be ok. You'll either have to have the same lib/perl directory for all the copies, or you'll have to watch out for syncronization problems where two developers change the same module. CVS or some other revision control system is going to be a MUST to keep each copy of the modules in sync if you go the separate directory route.

On a different note, the app server framework I developed supports dynamic loading of modules when they change (not going through Apache::Registry), thus eliminating the restart problem. And if a certain module chokes, it doesn't bring the server down (you just get an error message when you try to access it). The mechanism isn't that complicated, I can show you if you like.

Update Fixed grammer errors :)

/\/\averick
perl -l -e "eval pack('h*','072796e6470272f2c5f2c5166756279636b672');"

Comment on Re: Team development on mod_perl + apache

Replies are listed 'Best First'.
Re: Re: Team development on mod_perl + apache by mr.dunstan (Monk) on Feb 19, 2002 at 18:24 UTC
Yeah I would recommend everyone running on their own port, but keep everyone's development environment completely separate (even lib), and make sure all dev code is controlled by CVS. If the developers talk to each other enough they'll be able to work out any weirdness possibly resulting from changes to lib (hopefully anyone changing lib isn't going to hack-and-slash their way thru it ...) -mr.dunstan	[reply]
Re: Re: Re: Team development on mod_perl + apache by ignatz (Vicar) on Feb 19, 2002 at 18:50 UTC
++ One nice side effect of everyone using and building their own web server is that every one of the developers will know how to get the site up and running, so if things go wrong, any one of them can help out as opposed to the usual shrugging of shoulders and pointing of fingers. ()-() \"/ `	[reply]
Re: Re: Team development on mod_perl + apache by drewbie (Chaplain) on Mar 05, 2002 at 19:50 UTC
On a different note, the app server framework I developed supports dynamic loading of modules when they change (not going through Apache::Registry), thus eliminating the restart problem. Why not just use Apache::Reload or Apache::StatINC? They accomplish exactly the same thing as you describe above. A:Reload also allows selective reloading of modules IIC. But they also have the advantage of having been around a while & well tested. Is there something special your module does? I love to reinvent the wheel myself, but sometimes it's better not to do so. :-)	[reply]