Re: steps for synchronizing with production server

On May 19, 2009, at 23:22, webpost_at_tigris.org wrote:

> What are the best steps for updating a local SVN with changes from
> production? We've got 20GB of files and on a last attempt, ended up
> with old repo (.svn) folders and a mess.
>
> Is there a more efficient way to migrate changes to the dev
> repository? Thanks for any advise.
>
> 1.) Copy PROD to LOCALPROD
> 2.) Remove LOCALPROD svn entries
> $ find -name .svn -print | xargs rm -rf {}
> 3.) Remove LOCALPROD orphans
> .... ?
> 4.) Copy LOCALPROD over LOCALDEV
> $ cp -rf * LOCALDEV/*
> 5.) Update subversion repo
> $ su sync_user && svn update && svn commit -m'updating from
> production'

Your post is confusing due to the use of the wrong term... I'm pretty
sure you're talking about copying and updating *working copies*, not
*repositories*.

Does your production server have access to the repository? If so,
your update process could be as simple as having a working copy on
the production server, on which you run "svn up" when you want to
update it.

If that doesn't work for you, you should describe your setup in more
detail. For example, what do you mean by ending up with "a mess"?
What steps led to it?

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2325812

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-20 08:36:00 CEST