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

Re: File access control

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Fri, 30 Sep 2011 20:53:19 -0500

On Fri, Sep 30, 2011 at 8:46 PM, Grant <emailgrant_at_gmail.com> wrote:
>
> My workflow above only describes a single repository on the dev
> machine, the production machine wouldn't have a repository.  rsync
> would synchronize the source files, not the repository.
>

Normally you would do that with a subversion client, creating
different workspaces for development, testing, and production with
commit/update operations to move data instead of rsync. Variations
on that are possible, but you really don't want to set up a path that
has a way to get something into production that wasn't committed as a
known revision or tag. Rsyncing from a test/staging copy to
production is probably ok - going straight from the development
workspace where changes are being made would be more risky.

-- 
   Les Mikesell
     lesmikesell_at_gmail.com
Received on 2011-10-01 07:53:52 CEST

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

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