Loading Profile...
SVN+SSH with Capistrano
I've recently been looking in to moving some of my SVN repositories over to Beanstalk - it looks like a great little app and looks like it could be very useful.
I've got a quick question about SVN+SSH checkout with Beanstalk.
With my current setup I use Capistrano to deploy my Rails apps and that uses SVN+SSH to checkout the latest revision of my code.
It looks something like this "svn+ssh://user@domain.com/~/svn/repository/trunk"
Does Beanstalk allow this kind of access, and if not do you have any suggestions as to how I might configure Capistrano to work with your set up?
Thanks,
Mike.
I've got a quick question about SVN+SSH checkout with Beanstalk.
With my current setup I use Capistrano to deploy my Rails apps and that uses SVN+SSH to checkout the latest revision of my code.
It looks something like this "svn+ssh://user@domain.com/~/svn/repository/trunk"
Does Beanstalk allow this kind of access, and if not do you have any suggestions as to how I might configure Capistrano to work with your set up?
Thanks,
Mike.
I’m curious!
1 person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The best answer from the company
-
Hi.
We use Capistrano in Beanstalk too. Just put this in your deployment recipe:
set :repository, "http://svn.*.beanstalkapp.com/repo1/trunk/application"
Then, create a read-only user in beanstalk, and you'll be set.
In our case, it didn't involve any additional setup, since we use same authentication credentials for svn as we use for ssh, so there's no need to specify svn password separately. But if you want to I think Capistrano has an option for this.
An advantage of svn+ssh way is that it's more secure, but it's more difficult to setup and harder to manage user permissions, since after connection made it through SSH, it's just becomes a raw file access to a filesystem, skipping all the authz files. Feels wrong to me.
Security problem of http way can be solved by using https to connect to svn and we are moving in that direction. SSL access should be available this week. It's a shame it took us so long.
The company and 1 other person say
this answers the question
-
Inappropriate?Hi.
We use Capistrano in Beanstalk too. Just put this in your deployment recipe:
set :repository, "http://svn.*.beanstalkapp.com/repo1/trunk/application"
Then, create a read-only user in beanstalk, and you'll be set.
In our case, it didn't involve any additional setup, since we use same authentication credentials for svn as we use for ssh, so there's no need to specify svn password separately. But if you want to I think Capistrano has an option for this.
An advantage of svn+ssh way is that it's more secure, but it's more difficult to setup and harder to manage user permissions, since after connection made it through SSH, it's just becomes a raw file access to a filesystem, skipping all the authz files. Feels wrong to me.
Security problem of http way can be solved by using https to connect to svn and we are moving in that direction. SSL access should be available this week. It's a shame it took us so long.
The company and 1 other person say
this answers the question
-
Inappropriate?Thanks for the prompt reply.
Sounds like the method you've suggested will work perfectly!
I’m thankful
EMPLOYEE