Skip to content

remote_usage.md

Latest commit

 

History

History
125 lines (88 loc) · 2.9 KB

remote_usage.md

File metadata and controls

125 lines (88 loc) · 2.9 KB

FW Victron - Remote usage

Here a list of common procedures to test and run this script to a remote machine:

Copy sources to remote machine

  1. Connect and create dir into remote machine
$ ssh pi@raspberrypi.local
(rpi)$ mkdir -p dev/fw_victron
(rpi)$ exit
  1. Copy local sources to remote machine
$ rsync -av --exclude venv --exclude logs --exclude __pycache__ --exclude .git -e ssh * pi@raspberrypi.local:/home/pi/dev/fw_victron

Prepare remote machine (only once)

  1. Connect to remote machine
$ ssh pi@raspberrypi.local
  1. Install requirements (only once)
(rpi)$ sudo apt-get install python3 python3-pip libcairo2-dev libgirepository1.0-dev dbus-x11
  1. Install python's requirements (only once)
(rpi)$ cd dev/fw_victron
(rpi)$ python -m venv venv           # Optional: only for venv support
(rpi)$ source venv/bin/activate      # Optional: only for venv support
(rpi-venv)$ pip install -r requirements.txt

Run on remote machine

  1. Connect to remote machine and cd to firmware dir
$ ssh pi@raspberrypi.local
(rpi)$ cd dev/fw_victron
  1. Init DBus session (only if required)
(rpi)$ env | grep DBUS_SESSION_BUS_ADDRESS
# no response means the DBus session is required
(rpi)$ exec dbus-run-session -- bash
(rpi)$ env | grep DBUS_SESSION_BUS_ADDRESS
# copy the printed output as DBUS Session
  1. Activate the venv (if required)
(rpi)$ source venv/bin/activate
  1. Run the Python script
(rpi)$ python run.py

Monitor DBus from 2nd shell

  1. Connect to remote machine with another shell
$ ssh pi@raspberrypi.local
  1. Set DBus session, using the value copied after his creation
(rpi2)$ export DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-Qzp4nPaFAr,guid=88e4d61b4af3628519f04ede651e6f7f
  1. Start the dbus monitor
(rpi2)$ dbus-monitor

Configure SSH keys to avoid password usage

  1. Create a 'public_keys' on the remote machine
$ ssh pi@raspberrypi.local
(rpi)$ mkdir -p .ssh/public_keys
(rpi)$ exit
  1. Generate a new key pair and copy the public one on the remote machine
$ ssh-keygen -t rsa
#  save it in /home/USER/.ssh/id_rsa_for_rpi
$ scp /home/USER/.ssh/id_rsa_for_rpi.pub pi@raspberrypi.local:/home/pi/.ssh/public_keys
  1. Set up the new public key into remote machine
$ ssh pi@raspberrypi.local
(rpi)$ cat .ssh/pub_keys/id_rsa_for_rpi.pub >> .ssh/authorized_keys