Differences

This shows you the differences between two versions of the page.

--- syncthing [2022/09/09 04:23] – Add troubleshooting/advanced config atari
+++ syncthing [2025/04/08 16:17] (current) – peterbozso
@@ Line 20: / Line 20: @@
 ==== Initial setup ====
-First, you need to enable Syncthing on all the Batocera machines you want to use for saves synchronization. On each Batocera machine, edit the ''/userdata/system/batocera.conf'' file and add:
+First, enable Syncthing on all the Batocera machines you want to use for saves synchronization.
+On each machine with Batocera v38 and higher, execute the command:
+   batocera-services enable syncthing
+On each machine with Batocera v37 and lower, edit the ''/userdata/system/batocera.conf'' file and add:
    system.syncthing.enabled=1
-Once this is done, reboot your Batocera. When your Batocera is back up, on another computer on your local network open a web browser to ''http://batocera:8384'' (where "batocera" is the IP address of your machine, if the DNS is not up).
+Once this is done, reboot Batocera. When Batocera is back up, on another computer on the same local network, open a web browser to ''http://batocera:8384'' (where "batocera" is the IP address of your machine, if the DNS is not up).
 You will have a Synthing web UI where the configuration process start.
@@ Line 34: / Line 40: @@
 Now let's move on to the configuration:
   - Settings: this is the main page where you can define a Syncthing name for your Batocera unit, and on the GUI tab you can put a login/password to protect access to this web configuration page on ''http://batocera:8384''. I would strongly encourage you to put a login and password in there.<WRAP center round help>
-In Batocera **v33**, if **ENFORCE SECURITY** is "ON" then the Syncthing web UI <wrap em>cannot be accessed externally</wrap>. Disable this setting to regain access to it externally.
+In Batocera **v33**, if **ENFORCE SECURITY** is "ON" then the Syncthing web UI cannot be accessed externally. To circumvent this, two options:
+. Disable this setting to regain access to it externally.
+. Or create a SSH tunnel from another machine.
+For example, on a Linux host you can ''ssh -L 3000:127.0.0.1:8384 root@batocera'' and it creates a SSH session with local port 3000 mapped to port 8384 on the Batocera machine. This way, within the SSH session once you are connected, you can go to ''http://127.0.0.1:3000/'' on your Linux host and it will show the Syncthing configuration UI on the Batocera machine. If you use Windows, Putty also has an option to create SSH tunnels.
 </WRAP>\\ {{::syncthing_2_settings_main.png?direct&720|}}
   - Once you have this basic setup done on at least two Syncthing nodes (i.e. two Batocera machines with Synchthing on, or a Batocera + your central server for saves), you can create a cluster of Syncthing nodes, by telling each node which are the other machines where you want to share your saved files. Click **Add Remote Device...**. You can add a friendly name for each machine, internally Syncthing identifies them with a self-generated ''DeviceID''. This also is where you would set the **Introducer** option if connecting to an always-online NAS.\\ {{::syncthing_3_add_device.png?direct&720|}}
@@ Line 40: / Line 51: @@
   - Then on the "sharing" tab of the same screen, you can select all the nodes you want to synchronize this Batocera saves folder with.\\ {{::syncthing_5_sharing_folder.png?direct&720|}}
   - You need to repeat that on all nodes, but if your nodes are on the same network, they might be auto-discovered and announce their shared folders to the other nodes to provide a one-click easy addition.\\ {{::syncthing_6_shared_folder.png?direct&720|}}
-  - If you run Batocera on a PC x86_64, as well as other SBC, there might be save folders you want to ignore for the synchronization. Typically, flatpak and Windows games aren't necessary on a SBC and eat up quite a lot of storage. So, you can define some patterns that you want to ignore. On my PC x86_64, I put ''flatpak/'' and ''windows/'' to ignore these folders, without deleting them. On my SBC, I put ''(?d)flatpak/'' and ''(?d)windows/'' with ''(?d)'' meaning that the directories **can be deleted** if they are deleted in the syncthing cluster. **Be careful** with this option, if used incorrectly you may lose data.\\ {{:syncthing_9_ignore.png?direct&720|}}
+  - If you run Batocera on a PC x86_64, as well as other SBC, there might be save folders you want to ignore for the synchronization. Typically, flatpak and Windows games aren't necessary on a SBC and eat up quite a lot of storage. So, you can define some patterns that you want to ignore. On my PC x86_64, I put ''flatpak/'' and ''windows/'' to ignore these folders, without deleting them. On my SBC, I put ''(?d)flatpak/'' and ''(?d)windows/'' with ''(?d)'' meaning that the directories **can be deleted** if they are deleted in the syncthing cluster. **Be careful** with this option, if used incorrectly you may lose data.\\ {{:syncthing_9_ignore.png?direct&720|}} <WRAP center round info>
+The ignore syntax is very powerful, its full documentation is available at https://docs.syncthing.net/users/ignoring and should be read before attempting to use this.
+</WRAP>
   - Once the shares are configured, you should see on the UI a progress for the initial synchronization. Depending on the size of your shared files, it might take some time, but you can follow the process on this screen.\\ {{::syncthing_7_progress.png?direct&720|}}
@@ Line 67: / Line 80: @@
 Further help can be found at [[https://docs.syncthing.net|Syncthing's documentation]].
+===== Generic cloud backup =====
+https://gitlab.com/peterbozso/batocera-backup-service
+The use-case of this solution is very similar to [[:syncthing|Syncthing]], but the goal here is to utilize cloud storage (OneDrive, Google Drive, Dropbox, etc.) to back up your data. The important difference is that this is **upload only**; it does not synchronize data both ways. It is for continously cloning a single machine's userdata to the cloud service, so in case of a hardware failure/loss, a backup of the userdata can be easily restored.
+This solution uses [[https://rclone.org/|rclone]], which is shipped with Batocera and [[launch_a_script#services|Batocera's services feature]]. Because of the latter, it requires Batocera **v40** or higher.
+A detailed description of how this works and setup instructions for it is on [[https://gitlab.com/peterbozso/batocera-backup-service|peterbozso's batocera-backup-service repository]].