Thanks for the great replies Jamis and David.
On Feb 12, 1:44 pm, "David Masover" <[EMAIL PROTECTED]>
wrote:
> 'Capguy' isn't such a bad idea, particularly if they only have read access.
> As far as I know, Capistrano will never do a commit, and anyone who can read
> the 'capguy' credentials has at least as much access as capguy does.
>
> It might also be possible to do tricky things like:
>
> set :repository, "svn+ssh://[EMAIL PROTECTED]/..."
>
> That will only work on Unix hosts, though, and only if your username is the
> same.
>
> Another possibility is tricky things with svn:keywords. Does the $HeadURL$
> keyword have the username in there? If so, here's what I've been doing:
>
> set :repository do
> # This will not work if you check this file out of a path with
> apostrophes.
> # But that would not be a valid URI anyway, I think.
> '$HeadURL$' =~ /^\$[H]eadURL: +(https?:\/\/.*)\/config\/deploy.rb +\$$/
> $1
> end
>
> You'll have to swap that https for svn+ssh, or whatever will actually match
> HeadURL.
>
> Worst case -- if you can't find any way to automagically figure out who the
> developer is -- separate it out into a separate, unversioned file that each
> developer has to create. It could be as simple as:
>
> set :user, 'jsmith'
>
> On 2/12/08, eric <[EMAIL PROTECTED]> wrote:
>
>
>
> > 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
> > developers who need to deploy probably have different usernames for svn
> > +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
-~----------~----~----~----~------~----~------~--~---
