Could do with adopting this for the 'sudo' function. Currently that
breaks if you try and run a pipeline with it.
It runs as
(sudo command) || next_command
rather than
sudo (command || next_command)
Jamis Buck wrote:
Might be nice to encapsulate this somehow for multiline scripts.
I'm having a problem with Capistrano. I'm deploying from my box (which
is also the repository right now) as myself. I have a user on my box
called webuser2, which has access to the repository. I'm deploying
to deployserver as user webuser2. On the repo box (my box), I have
a ssh key for
It is possible to svn+ssh into your own box...but you have to make
sure you've got everything configured to allow svn+ssh to your own
box. I'm not an svn config guru, though, so I can't help you.
Probably you'd have better luck with this kind of question on a
subversion mailing list. If
Alternatively you could use my new subversion SCM module, which only
accesses
the subversion repository from your local workstation.
This would eliminate the need for your server to call back into your
workstation, and avoid the
potential firewall issues, ssh authentication issues and such.
Well, I got to the core of what was happening by attempting several
ways of svn list ing the repo on my box. The problem was that, as I
mentioned earlier, users who access svn on my box do so via ssh, and
they authenticate using an ssh key. Their public keys on my box
contain the line
NeilW wrote:
My line takes a shell script stored on the command station, uploads it
to the server, runs it and then removes it.
Your line takes a script that has already been deployed on the servers
and runs it, leaving the script in place.
Sure, I understand that, I guess I was being a
