Re: 'good practices' in php programming with subversion

brunoml wrote:
>> 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...)

There is no need fo that. You just need a server with remote php
debugger (Zend recommended).

What we use in company where I work is CVS server on one machine, and
all developers commit there.

On every commit CVS runs post-commit script that connects to debug
server with apache, php and zend debugger, updates cvs managed content
with cvs update and then developers can debug directly on server.

Works like a charm.

BTW developers do not need apache on their windows machines, IIS works
just the same.

---------------------------------------------------------------------
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:25:07 2006