perryn escribió:
Does anyone know why capistrano is not loading .profile on ssh login,
and if here is anything I can do about that?
What shell are you using? I think that .bashrc in bash shells is loaded.
Regards
--
Rafael Garcia Ortega
I'm using bash, but .bashrc doesn't seem to be picked up either ( or
perhaps it is, but the aliases in it are ignored - its hard to tell)
I'm wondering if capistrano is running the tar command from a sftp
session, and wether that has something to do with it..
If you are running without a pseudo-tty (the default), it _should_
autoload your profile info. However, all bets are off with Solaris--it
does so many things differently that I don't even try to keep up
anymore. :(
Note, though, that running without a pty can cause problems of its
own.
you can set the PATH variable in the default environment in your
deploy.rb:
default_environment[PATH] = /usr/bin:/usr/local/bin:/opt/local/
bin:...
This is what finally worked -
I made a new directory on the deployment box called capistrano-
links,
made a softlink called tar to the
perryn escribió:
Hello,
So I'm trying to deploy to a Solaris box using deploy_via :copy
It doesn't work, because tar on the target box doesn't understand the
z option, so I need to use gtar instead.
I aliased tar to gtar in my .profile, but it seems this is not getting
run by capistrano.
Hi Rafael,
Wow, thanks for the detailed and helpful answer - I was hoping to
avoid having to override capistrano for such a niggly little problem,
but this will be a great help If I have to go that way.
Does anyone know why capistrano is not loading .profile on ssh login,
and if here is
On 2/9/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On Jan 6, 12:04 pm, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Just a heads up to anyone using cap to deploy apps on Solaris...
I ran into problems with the symlink task... It would end up creating
links to the new release inside
The solution sort-of worked for me. The problem is the deploy dies
first time out since current_path doesn't yet exist.
I wound up adding an :after_setup that touches current_path so it
exists when deploy calls symlink.
Is there a way to get commands strung together with to run if the
prior
Try using rm -f instead of just rm when removing the
current_path. That should make it more robust (though the two-step
remove+link means your deploys will no longer be atomic... too bad
solaris has to do it's own thing in so many ways).
- Jamis
On Feb 8, 2007, at 4:27 PM, Steve Downey
