# Off - subversion

**URL:** <https://www.ruby-forum.com/t/off-subversion/102001>\
**Category:** Rails\
**Created:** [August 9, 2006, 7:01am UTC](https://www.ruby-forum.com/t/off-subversion/102001 "2006-08-09T07:01:15Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![pieter](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/82dd89/32.png) [@pieter](https://www.ruby-forum.com/u/pieter)\
**Post date:** [August 9, 2006, 7:01am UTC](https://www.ruby-forum.com/t/off-subversion/102001/1 "2006-08-09T07:01:15Z")

</div>

hi guys

question on usage of subversion.  
just set up the repository, removed database settings, logs, tmp etc  
from being committed. we are two developers and a designer working on  
the project.  
do not have the luxury of a separate development and production server.  
(cost of bandwidth in 3rd world countries!)

figured out how to allow everyone involved to checkout latest version  
and check in their changes, but how do i actually commit a specific  
version to the ‘live’ site? running on the same machine say in  
/var/www/data/app/ ???

happy railing.

pb.

---

<div class="post-metadata">

**Author:** ![pieter](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/82dd89/32.png) [@pieter](https://www.ruby-forum.com/u/pieter)\
**Post date:** [August 9, 2006, 7:38am UTC](https://www.ruby-forum.com/t/off-subversion/102001/2 "2006-08-09T07:38:15Z")

</div>

Pieter B. wrote:

> hi guys
> 
> question on usage of subversion.  
> just set up the repository, removed database settings, logs, tmp etc  
> from being committed. we are two developers and a designer working on  
> the project.  
> do not have the luxury of a separate development and production server.  
> (cost of bandwidth in 3rd world countries!)
> 
> figured out how to allow everyone involved to checkout latest version  
> and check in their changes, but how do i actually commit a specific  
> version to the ‘live’ site? running on the same machine say in  
> /var/www/data/app/ ???
> 
> happy railing.
> 
> pb.

Well, you probably shouldn’t be deploying every single change to the  
production environment directory. The best thing to do would be to  
identify your revision you want to release, tag it, and then export it  
(svn export) into the production directory. If you really are wanting a  
commit-for-commit copy in production, you might want to look at using a  
post-commit hook to export the HEAD revision automatically.

---

<div class="post-metadata">

**Author:** ![pieter](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/82dd89/32.png) [@pieter](https://www.ruby-forum.com/u/pieter)\
**Post date:** [August 15, 2006, 2:11pm UTC](https://www.ruby-forum.com/t/off-subversion/102001/3 "2006-08-15T14:11:49Z")

</div>

> question on usage of subversion.  
> just set up the repository, removed database settings, logs, tmp etc from  
> being committed. we are two developers and a designer working on the project.  
> do not have the luxury of a separate development and production server. (cost  
> of bandwidth in 3rd world countries!)
> 
> figured out how to allow everyone involved to checkout latest version and  
> check in their changes, but how do i actually commit a specific version to  
> the ‘live’ site? running on the same machine say in /var/www/data/app/ ???

Well, if /var/www/data/app is a svn working directory, just update it to  
the revision you want…

-philip

---

<div class="post-metadata">

**Author:** ![pieter](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/82dd89/32.png) [@pieter](https://www.ruby-forum.com/u/pieter)\
**Post date:** [August 15, 2006, 2:19pm UTC](https://www.ruby-forum.com/t/off-subversion/102001/4 "2006-08-15T14:19:22Z")

</div>

I would suggest you take a look at using capistrano scripts.  
[Peak Obsession](http://manuals.rubyonrails.com/read/book/17).  
~  
Michael Fairchild  
removed\_email\_address@domain.invalid  
UCLA Particle Beam Physics Lab

---

<div class="post-metadata">

**Author:** ![pieter](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/82dd89/32.png) [@pieter](https://www.ruby-forum.com/u/pieter)\
**Post date:** [September 4, 2006, 2:45pm UTC](https://www.ruby-forum.com/t/off-subversion/102001/5 "2006-09-04T14:45:31Z")

</div>

It’s better and easier to do a checkout and protect the .svn directories  
from  
being served. If you need a do a rollback, then you use ‘svn update -r  
OLDER\_REVISION’ or ‘svn update -r PREV’.

Also, you can use Capistrano to do deployments.

Regards,  
Blair

---

<div class="post-metadata">

**Author:** ![pieter](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/82dd89/32.png) [@pieter](https://www.ruby-forum.com/u/pieter)\
**Post date:** [August 15, 2006, 2:19pm UTC](https://www.ruby-forum.com/t/off-subversion/102001/6 "2006-08-15T14:19:22Z")

</div>

Why not just export the code to your live site? You can use the svn  
export command to do this. It retrieves the code from the repository for  
uses other than a working copy.