[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: Relationship between repository and production code

From: Steve Swift <steve.j.swift_at_gmail.com>
Date: Tue, 29 May 2012 04:37:30 -0700 (PDT)

> If you need a more controlled update process, you can just
> copy your scripts up to the server like you always have, or establish
> a working copy there which you manually update.

I'll play with these ideas, thanks. We already have a test directory and a live directory on the server, with mechanisms to copy changes ftom test to live, so I'll probably make the test directory a working copy.

So my process will be:

1. Change local working copy
2. Commit, which automatically updated the test directory on the apache server
3. Test the code via apache, using the test directory
4. Copy it to production

I can see that I'm going to love SVN.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-05-29 13:37:36 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.