On Tue, Mar 05, 2002 at 02:54:47PM -0800, Paul Lindner wrote:
> On Tue, Mar 05, 2002 at 04:53:56PM -0600, Dave Rolsky wrote:
> > On Tue, 5 Mar 2002, Medi Montaseri wrote:
> >
> > > My suggestion would be to install a Linux on your developer's PC and
> > > keep with the distributed model. Now ever
wow crazy!!
just got my email and saw this thread!
did anyone post on their site?
again that node:
http://perlmonks.org/?node_id=146303
Wim Kerkhoff wrote:
>I'm jumping into this thread quite lately, but here are my $.03 CDN.
>
>Mark Fowler wrote:
>
>>On Tue, 5 Mar 2002, Medi Montaseri wrote:
Unfortunately, this may also allow the developer to potentially change
code/configuration that you do not want changed.
> True...but I'm thinking full control to the developer. Developer can now
> mis-configure httpd.conf as much as he/she wants and all the paths;
> virtual or not are consistant,
I'm jumping into this thread quite lately, but here are my $.03 CDN.
Mark Fowler wrote:
>
> On Tue, 5 Mar 2002, Medi Montaseri wrote:
>
> > Stuart Frew wrote:
> >
> > > Ideally you would have linux( or what ever) on every developers
> > > machine but sometimes you don't get the choice.
> >
> >
On Tue, 5 Mar 2002, Medi Montaseri wrote:
> Stuart Frew wrote:
>
> > Ideally you would have linux( or what ever) on every developers
> > machine but sometimes you don't get the choice.
>
> Oh "the choice" is easyjust come in on a weekend and install
> linux on your box. Don't tell IT. That'
Stuart Frew wrote:
Greeting,
Ideally you would have linux( or what ever) on every developers machine
but sometimes you don't get the choice.
Oh "the choice" is easyjust come in on a weekend and install
linux on your box. Don't tell IT. That's all.
Cheers
On Wed, 2002-03-06 at 13:40, Med
Hello,
PL>One other tip... write a small script (or modify apachectl) to start
PL>apache with a port number matched to your unix UID. This keeps
PL>developers from using clashing port numbers.
PL>
PL> httpd -c "Port $UID" -c "Listen $UID"
At Tellme we find it easiest to run multiple Apaches, o
Greeting,
Yup, I agree but I meant virtual hosts on the development box, not production.
Ideally you would have linux( or what ever) on every developers machine but sometimes you don't get the choice.
Cheers
On Wed, 2002-03-06 at 13:40, Medi Montaseri wrote:
I don't agre
On Tue, 5 Mar 2002, Medi Montaseri wrote:
> True...but I'm thinking full control to the developer. Developer can now
> mis-configure httpd.conf as much as he/she wants and all the paths;
> virtual or not are consistant, instead of a dev path vs production path
Right, every developer can run
I don't agree with virtual hosts setup for mod_perl folks. What if
someone mess up the configuration file. If you want a central person
to change them, then you are limitting the developer.
The Linux-on-developers-box proposition also goes to include a
database instance for the developer to cras
True...but I'm thinking full control to the developer. Developer can now
mis-configure httpd.conf as much as he/she wants and all the paths;
virtual or not are consistant, instead of a dev path vs production path
I had a chance to work with Interwoven TeamSite and this very issue or
virtual p
Greetings,
Depending on the number of developers and how often they change, virtual hosts are good.
Set up a sub-domain for each developer, ie jim.my-company.co.nz.
Then they can configure there local setup to there hearts content, seperate CVS/document tree, also get separate logs.
C
On Wed, 6 Mar 2002, Gunther Birznieks wrote:
> Philippe Chiasson had a really nice talk on setting up developer teams on
> mod_perl at ApacheCon 2001. Covers everything from CVS to deployment. You
> may want to see if you can get the slides from him ([EMAIL PROTECTED]) if you
> are interested
Medi Montaseri wrote:
> Caller can also buy some content management software like Interwoven's
> TeamSite
> product that provides a virtual workarea, for about $300,000.
It's so easy and effective to run mod_perl on developers' personal
machines, I think there's no excuse not to do it.
At eToy
Philippe Chiasson had a really nice talk on setting up developer teams on
mod_perl at ApacheCon 2001. Covers everything from CVS to deployment. You
may want to see if you can get the slides from him ([EMAIL PROTECTED]) if you
are interested in the details.
Later,
Gunther
At 07:43 AM 3/6/20
On Tue, Mar 05, 2002 at 04:53:56PM -0600, Dave Rolsky wrote:
> On Tue, 5 Mar 2002, Medi Montaseri wrote:
>
> > My suggestion would be to install a Linux on your developer's PC and
> > keep with the distributed model. Now everyone can use a common web tree
> > and at integeration, bring all of the
On Tue, 5 Mar 2002, Medi Montaseri wrote:
> My suggestion would be to install a Linux on your developer's PC and
> keep with the distributed model. Now everyone can use a common web tree
> and at integeration, bring all of them to a staging box, QC it and ship
> it to production.
Giving everyone
Caller wirtes
> we've just migrated our 80K line pure perl web application to mod_perl...ah...
> so much aster... can anyone advise on their experiences for setting
up
> apache/mod_perl for team development? up till now, we've all been
running
> our own copy of sources out of our home directo
18 matches
Mail list logo
