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.
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. On Tue, 2006-08-08 at 23:45 +0200, Pieter Botha 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. > > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails
Pieter Botha 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. -- Posted via http://www.ruby-forum.com/.
I would suggest you take a look at using capistrano scripts. http://manuals.rubyonrails.com/read/book/17. ~ Michael Fairchild fairchild@pbpl.physics.ucla.edu UCLA Particle Beam Physics Lab On Aug 8, 2006, at 10:38 PM, Cody Maggard wrote:> Pieter Botha 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. > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060809/a2a4eeee/attachment-0001.html
> 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
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 Jeff Cabaniss wrote:> 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. > > On Tue, 2006-08-08 at 23:45 +0200, Pieter Botha 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.