rumble's dashboard

Thanks for the prompt reply.

Sounds like the method you've suggested will work perfectly!

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.