[Capistrano] Re: Weird problem when deploying

[Jamis Buck]

Note that cap (by default) queries svn from both the local and remote hosts, so you'd need that tunnel definition in both places. If you're using a deployment strategy like :copy, which only queries svn from the local host, you'd only need the definition locally.

- Jamis

On Oct 24, 2007, at 1:28 PM, Stephan Schubert wrote:

Okay, i finally found a solution:

The problem is the command the tunnel does/should invoke:
(in my /home/svn/.ssh/authorized_keys)

command="/usr/local/lib/svnserve -t --tunnel-user=stephan -r /var/
svnrepos", ... key, etc

I used the -r option so i can omit /var/svnrepos in my URLs - but
obviously this does not
work when using Capistrano - for whatever reason :)

So, remove the -r option and use the "full" URL to the repository
solves this issue.
I don't really know what the real cause of this issue is - but after
accumulated 6-7 hours
of pulling my hair out - i'm glad it works now. ;)

Doing it manually on the host works, let Capistrano do it won't.
Perhaps some SVN magic?

Anyway, i hope this will get indexed by Google and help others
struggeling with it.

Greets,
Stephan


--~--~---------~--~----~------------~-------~--~----~

To unsubscribe from this group, send email to capistrano- [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/ group/capistrano

-~----------~----~----~----~------~----~------~--~---

smime.p7s
Description: S/MIME cryptographic signature