I spent all morning figuring out how to get the remote execution of Python scripts working.\u00a0 What a PITA!<\/p>\n
It turns out that when you log in through SSH, or in my case SFTP, you get handed a completely PATH environment variable that if you log in locally or through a Virtual Private Network.\u00a0 That results in the remote system not being able to find commands that it normally as access to via modifications to the user’s .profile or .bashrc files.\u00a0 When coming in through sftp, none of those modifications are read or applied.<\/p>\n
I tried many things and finally got it working by:<\/p>\n
Now, I can use pysftp to execute any properly formatted python programs that can be found on the new PATH.<\/p>\n
I could have executed the programs by simply using the full path to the program in the sftp.execute command (as long as permissions were set correctly) but I wanted a cleaner solution.<\/p>\n
What I have done would not be the most secure setup if there were actually different users but in my situation I am all the users so no big deal.\u00a0 The potential security issue is because now each user can alter their SSH environment variables.<\/p>\n
By the way, connecting up the sensor won’t happen until at least 12\/22 because some of the required parts have been delayed.\u00a0 If UPS decides the roads are too icy for them it may not happen for a few days.<\/p>\n
Glad I got it working!\u00a0 I need a break!<\/p>\n","protected":false},"excerpt":{"rendered":"
I spent all morning figuring out how to get the remote execution of Python scripts working.\u00a0 What a PITA! It turns out that when you log in through SSH, or in my case SFTP, you get handed a completely PATH … Continue reading