How do you tried it[http://www.capify.org/index.php/Path_Problems] ?
More info from http://www.capify.org/index.php/Run:
:pty
If true, a pseudo-tty will be allocated for each command. The default is
false. Note that there are benefits and drawbacks both ways.
Empirically, it appears that if a pty is allocated, most SSH server
daemons will not read user shell start-up scripts (e.g. bashrc, etc.).
However, if a pty is not allocated, some commands (like sudo, or git, or
svn) will run in non-interactive mode and will not prompt for (e.g.)
passwords. You have to choose your poison, apparently.
Good night
BJ Neilsen wrote:
Hi Nick,
When you ran the command manually were you logged in as deployer?
Yes, I was ssh'd into the server as the deployer user.
It could be that deployer doesn't have bundle in its path.
You could try using cap shell and running `which bundle` to see if it is in the
environment that capistrano runs in.
Running `which bundle` as the deployer user gives me a path. Running it in cap
shell fails. You can see the output of both commands by seeing this gist[2]. My
thought is that one login uses a bash login and the other uses an interactive
shell, and that the gem path isn't setup properly in one of those two, but I'm
not sure if that is true.
BJ
[2] http://gist.github.com/295260
--
Rafa
--
* You received this message because you are subscribed to the Google Groups
"Capistrano" group.
* To post to this group, send email to [email protected]
* To unsubscribe from this group, send email to
[email protected] For more options, visit this group at
http://groups.google.com/group/capistrano?hl=en
