Re: Re: Relationship between repository and production code

On Tue, May 29, 2012 at 7:37 AM, Steve Swift <steve.j.swift_at_gmail.com> wrote:
>> 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

But copy it from where? Your test server? What if someone with access
to that server changes your code to "fix" a bug? Now what you've
copied to production doesn't match what's in the repository.

Copy from Subversion? What if you've committed other changes that
haven't been fully tested yet?

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2968282

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-06-02 03:13:37 CEST