Bash – Including .bash_profile over ssh

bashrcssh

I am trying to write a script that will:

Copy files to a server (I already have a script copy.sh that does this task)
ssh to that server
cd to the directory where the files I just copied are
run make
copy the resulting binary from make to another location.

My script looks like this:

#!/usr/bin/bash
BUILDSERV=me@server
BUILDDIR=/me/directory

#run my script that copies the files
./copy.sh

#TARGET is also a var in copy.sh so I make sure it's set properly here
TARGET=root@final_dest:/usr/bin/my_bin

ssh $BUILDSERV "cd $BUILDDIR && make && scp ./my_bin $TARGET"

The issue is that a program I want to run as part of make is not in my PATH. My .bash_profile has a export PATH=$PATH:/my/bin/ line, but it seems that bash_profile is not being read when I ssh in.

Is there a way to change my ssh invocation or script in general to make it read my .bash_profile?

Best Answer

The following should work:

ssh $BUILDSERV "source ~/.bash_profile && cd $BUILDDIR && make && scp ./my_bin $TARGET"

The source shell builtin reads a file and executed the commands in the same shell (unlike simply calling the script, which invokes a separate shell).

When invoked as login shell, bash executes the .bash_profile, if it exists, in exactly the same way as source does, therefore the effect will be the same.

Related Solutions

Ssh – the right file permission for a .pem file to SSH and SCP

Visit here How to Connect to Amazon EC2 Remotely Using SSH or refer below.

How to Connect to Amazon EC2 Remotely Using SSH:

Download the .pem file.
In Amazon Dashboard choose "Instances" from the left side bar, and then select the instance you would like to connect to.
Click on "Actions", then select "Connect"
Click on "Connect with a Standalone SSH Client"
Open up a Terminal window
Create a directory:
```
# mkdir -p ~/.ssh
```
Move the downloaded .pem file to the .ssh directory we just created:
```
# mv ~/Downloads/ec2private.pem ~/.ssh
```
Change the permissions of the .pem file so only the root user can read it:
```
# chmod 400 ~/.ssh/ec2private.pem
```

Create a config file:

# vim ~/.ssh/config

Enter the following text into that config file:

Host *amazonaws.com
IdentityFile ~/.ssh/ec2private.pem
User ec2-user

Save that file.

Use the ssh command with your public DNS hostname to connect to your instance.
e.g.:
```
# ssh ec2-54-23-23-23-34.example.amazonaws.com
```

SSH only works if I specify the key with -i

As far as I'm aware, ssh only searches for keys with the name id_rsa, id_dsa and a few others which all start id_ as show in the output in your question. If you have keys named anything else you must specify them on the command line, or in an ssh config file.

Either rename your file key to something ssh searches for, or update .ssh/config with a relevant stanza, or use the -i option.

You can use something like this in .ssh/config

host my.target.server
IdentityFile ~/.ssh/key

You can also use,

host *
IdentityFile ~/.ssh/key

to force ssh to use ~/.ssh/key for all connections.

It may be easier to rename the key file to id_dsa or id_rsa though (assuming the file is actually called key as in your output).

Best Answer

Related Solutions

Ssh – the right file permission for a .pem file to SSH and SCP

SSH only works if I specify the key with -i

Related Question