RE: Re: 'good practices' in php programming with subversion

> > My preference (and what we do with our Java web app):
> > Each dev has his own working copy
> > Each dev has, on his desktop, a unit testing environment
> > The central dev server is used for integration testing of
> all changes.
> > Code only gets to this server via svn checkout, developers cannot
> > copy files to it directly.
>
> Yes, but 'testing environment' mean apache+php on each dev desktop :-(
>
> This is what I would like to avoid... (but no better idea...)

Why not having the users's svn workspaces on a unix server accessible
- with samba to develop and do the svn operations,
- localy on the unix server by apache+php for the test purpose.

Christophe

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 24 16:08:09 2006