Lee Hambley

> I have always been relying on this ~/.bashrc behavior for my deployments. Interesting :) Let's keep this ticket then, it's tagged correctly at least and we can figure out...

I think it may be simplest to document that: - On some OS'es `~/.bashrc` is a convenient solution, but: - depending on your use-case there may be better alternatives such...

My only issue with `~/.bashrc`is that it's contrary to the docs: > By default Capistrano prefers to start a non-login, non-interactive shell, to try and isolate the environment and make...

I've been reading, and I think the original source graphic might conflict with @mattbrictson's observations: > In any case, this seems to confirm that bash (GNU bash version 4.3) does...

- https://www.gnu.org/software/bash/manual/html_node/Bash-Startup-Files.html

Would this read correctly from your point of view @mattbrictson : ? Green indicates the "normal" Capistrano case, and we can link directly the `Bash-Startup-Files.hmtl` docu from gnu.org

> Honestly I find that the flowchart is a bit overwhelming and I'm not sure if it will overall help people or make them more confused. I think it's because...

I think one thing that underpins this whole conversation is that people are so used to interacting with systems via a shell (Bash, Zsh, etc) that in environments that go...

> Also .bashrc and .profile were ignored. This is expected behaviour see the different (login vs. non-login, and interactive vs. non-interactive) shell modes depending on your OS and Capistrano configurations.

Closing because I’m not sure this is an issue, if you are convinced that this is really a bug, please feel free to re-open the issue and add more information...