# Capistano and SVN: Committing a change from the live copy?

**URL:** <https://www.ruby-forum.com/t/capistano-and-svn-committing-a-change-from-the-live-copy/149622>\
**Category:** Deployment\
**Created:** [September 26, 2008, 9:15pm UTC](https://www.ruby-forum.com/t/capistano-and-svn-committing-a-change-from-the-live-copy/149622 "2008-09-26T21:15:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![daveamos](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/a698b9/32.png) [@daveamos](https://www.ruby-forum.com/u/daveamos)\
**Post date:** [September 26, 2008, 9:15pm UTC](https://www.ruby-forum.com/t/capistano-and-svn-committing-a-change-from-the-live-copy/149622/1 "2008-09-26T21:15:30Z")

</div>

I’m sure this is an easy fix for folks more familiar with subversion  
than me, but here it goes:

I’m running Capistrano and have just successfully deployed my app from  
my local machine to my live server. The repository is on the server as  
well. What happened is I had to generate some files on the live server  
in the railsapp/current directory. So now when I try and commit  
something from my local machine, it says:  
svn: Commit failed (details follow):  
svn: Out of date: ‘/db’ in transaction ‘19-1’

Is it okay to commit changes made on the live machine to the repository?  
I guess I don’t understand the relationship of the live copy to the  
repository, especially in comparison to the local copy and the  
repository. It makes sense to me to just commit the changes I made on  
the live copy, then on my local copy check out the latest changes from  
the repository. Is that right?

Thanks!

Dave