I do not know if the environment the developers use is identical to the
environment of the production server, but otherwise it would be quite
useful to think about setting up a working copy on the production (or
better a development server) for testing purposes only. Especially for
web applications the environment is important for how the application
runs.
We use a development working copy which is automatically updated with a
post-commit hook script. We update the production server working copy by
hand when we have reached a stable version on the development server.
Hope this helps,
Maarten
On Sun, 2005-05-08 at 09:22 +0800, Sinang, Danny wrote:
> Dear Users,
>
>
>
> Am a newbie at this, so please bear with me.
>
>
>
> We have a server running SVN acting as our source code repository and
> we have another box running our production web application.
>
>
>
> If I understand it right, for any changes we want to effect on our
> production web application, our developers are supposed to :
>
>
>
> 1. Check-in all their web application source code changes to the
> SVN server
> 2. Check out an updated version of the web application
> 3. Post the web application source to the production web server
>
>
>
> Is there a better / faster / automated way than this ?
>
>
>
> Is it possible to configure SVN to update our production web server
> for every committed change ?
>
>
>
> Regards,
>
> Danny
>
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun May 8 06:42:42 2005