You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi - I've recently migrated my teslausb archive location from a Windows server CIFS/SMB share to a linux server. I was able to follow the instructions provided at this link to get syncing setup with one of our cars. Call it TESLA1. For this example I'm using [email protected] as the user for the Linux server.
Question -- when setting up a second car (TESLA2) to archive to the same server (192.168.x.x), am I able to reuse the authorized_keys file created for TESLA1? Essentially, I am trying not to undo the working sync already in place for TESLA1 when adding TESLA2 to the mix (i.e. overwriting files on the Linux server, etc.).
Providing more detail, my setup that was working with Windows and is moving to Linux:
Was specifically hoping I could just use the same user (root) and ideally the same key file(s) on TESLA2's pi and redirect to /tesla2 archive folder in the .conf file.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi - I've recently migrated my teslausb archive location from a Windows server CIFS/SMB share to a linux server. I was able to follow the instructions provided at this link to get syncing setup with one of our cars. Call it TESLA1. For this example I'm using [email protected] as the user for the Linux server.
https://github.com/marcone/teslausb/blob/main-dev/doc/SetupRSync.md#step-1-authentication
Question -- when setting up a second car (TESLA2) to archive to the same server (192.168.x.x), am I able to reuse the authorized_keys file created for TESLA1? Essentially, I am trying not to undo the working sync already in place for TESLA1 when adding TESLA2 to the mix (i.e. overwriting files on the Linux server, etc.).
Providing more detail, my setup that was working with Windows and is moving to Linux:
TESLA1 -> server: 192.168.x.x (admin/root) -> /tesla folder
TESLA2 -> server: 192.168.x.x (admin/root) -> /tesla2 folder
Was specifically hoping I could just use the same user (root) and ideally the same key file(s) on TESLA2's pi and redirect to /tesla2 archive folder in the .conf file.
Beta Was this translation helpful? Give feedback.
All reactions