[Capistrano] Re: Multiple users deploying using svn+ssh?

[Jamis Buck]

We just make sure our usernames are the same across the board, and it "just works." :)

Alternatively:



- Jamis

On Feb 12, 2008, at 11:20 AM, eric wrote:

set(:scm_username) { Capistrano::CLI.ui.ask("Yo! What's your svn username: ") }

Hello all,

I have a quick question.. actually, I'm probably more looking for
opinions.

Is anyone else deploying via Capistrano whilst using svn+ssh as their
SVN protocol?  If so, how do you handle the fact that all the

+ssh?  Is there a consensus opinion on how this should be done?  We've
got two ideas we've been bouncing around, and wonder if anyone else
has any better ideas.

1) Create a single user on the system, something like 'capguy', and
always have that user be the one that the repository uses.  example.

set :repository, "svn+ssh://[EMAIL PROTECTED]/usr/local/svn-
repositories/#{application}"

2) Just have the developers add in their own name after they do a svn
update and wish to deploy.

Are there any other 'better' ideas we're missing?  If not, which is
the system you use?

Any ideas/opinions would be great.

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

developers who need to deploy probably have different usernames for svn

smime.p7s
Description: S/MIME cryptographic signature