002d1e6f6c
Currently untested, but the main idea is there Currently it's either the normal archive server or rsync; not both, which is something to consider when adding things like gdrive and s3 (make it more modular?)
1.8 KiB
Introduction
This guide will show you how to utilize rsync to archive your saved TeslaCam footage on a remote storage server. In my case, I use this for a networked pi storage server.
This guide makes the following assumptions:
- You are running your own ftp/rsync server that you have admin rights to, or can at least add a public key to its
~/.ssh/authorized_keysfile - You have NOT run the
setup-teslacamscript yet
Step 1: Authentication
Similar to sftp, rsync by default utilizes ssh to connect to a remote server and transfer files. This guide will use a generated ssh keypair, hence the first assumption above.
On your teslausb pi, run ssh-keygen to generate an ssh key. Add the contents of the newly generated ~/.ssh/id_rsa.pub file from your teslausb pi to the storage server's ~/.ssh/authorized_keys file. This will allow a nice and easy connection through rsync, no passwords needed!
Step 2: Exports
To be able to configure the teslausb pi use rsync, you'll need to export a few things. On your teslausb pi, run:
export RSYNC_ENABLE=true
export RSYNC_USER=<ftp username>
export RSYNC_SERVER=<ftp IP/host>
export RSYNC_PATH=<destination path to save in>
Explanations for each:
RSYNC_ENABLE:truefor enabling rsyncRSYNC_USER: The user on the FTP serverRSYNC_SERVER: The IP address/hostname of the destination machineRSYNC_PATH: The path on the destination machine where the files will be saved
An example (of my) config is listed below:
export RSYNC_ENABLE=true
export RSYNC_USER=pi
export RSYNC_SERVER=192.168.1.254
export RSYNC_PATH=/mnt/PIHDD/TeslaCam/
Note: RSYNC_ENABLE=true is going to disable the default archive server. Perhaps future releases will allow both to be defined and function at the same time, for redundancy, but for now just pick one that you'll want the most.