RE: 368

Sorry, but I can’t comment when you close an issue. 🙏🏻

@mbierman source $HOME/.bash_profile is not a launching command because there isn’t any shell starting with .bash_profile

No, but there is a file. If I am in a shell on that device (a Mac) I can source the file and any changes made to it are now active in the shell.

Instead you could use bash -c “source $HOME/.bash_profile”

This also does not work. Eg.

#existing .bash_profile
...
echo "bash env is updated" 

Does not work and in fact I still can’t login at all to the machine if this is active via webssh. However, this works perfectly on the machine in terminal:

source  source $HOME/.bash_profile
bash env is updated

I won’t fix this issue because it’s not on WebSSH part it’s on your SSH server.

Sorry, what does this mean? Once I’m logged in shouldn’t I be able to execute any valid command that otherwise works on the Mac?

Moreover I don’t understand why launching source $HOME/.bash_profile command. Isn’t it launched by your shell at it startup?

I have a PATH set in my .bash_profile. If I don’t source it the path is not reflected so I can’t easily access some commands which is annoying. Setting it and sourcing a file seems like the normal, and easiest way to solve this. Is there a better way?

But setting the particular file aside, if I had any set of commands I wanted to run upon logging in can’t I source any file with valid commands?

[mbierman]

That does get me the path! .bashrc didn’t seem to execute though so my echo didn’t work, but that was just a test in this case. I wasn’t familiar with this option.

[isontheline]

Happy to hear that it solves your issue 👍

Thank you again for your feedback!