Differences

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

--- syncthing [2022/01/24 06:09] – enforce security not required 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 ''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.
 First, a few housekeeping items:
-  * do you allow to share encrypted usage data with Syncthing (Yes/No). Fully optional, and this data won't ever be shared with Batocera in any way, shape or form.
+  - do you allow to share encrypted usage data with Syncthing (Yes/No). Fully optional, and this data won't ever be shared with Batocera in any way, shape or form.\\ {{::syncthing_1_anonymous_usage.png?direct&720|}}
-{{ ::syncthing_1_anonymous_usage.png?direct&600 |}}
+  - A warning that the process should not run as a privileged user. At the moment, this is a limitation you need to accept to use Syncthing on Batocera.\\ {{::syncthing_1b_user.png?direct&720|}}
-  * A warning that the process should not run as a privileged user. At the moment, this is a limitation you need to accept to use Syncthing on Batocera.
-{{ ::syncthing_1b_user.png?direct&600 |}}
 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 cannot be accessed externally. To circumvent this, two options:
-  * 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.
+. Disable this setting to regain access to it externally.
-{{ ::syncthing_2_settings_main.png?direct&600 |}}
-  * 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. You can add a friendly name for each machine, internally Syncthing identifies them with a self-generated ''DeviceID''.
+. Or create a SSH tunnel from another machine.
-{{ ::syncthing_3_add_device.png?direct&600 |}}
+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|}}
-  * Now that we have our cluster of Syncthing nodes, we can configure the folders that need to be synchronized across them. In our example here, we want to synchronize the games save files in ''/userdata/saves/''. Be mindful of the ''folderID'' that is provided here. I kept the default one assigned by Synchthing, but you can put your own. What is important is that you keep the same ''folderID'' for all nodes in the cluster.
+  - 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|}}
-{{ ::syncthing_4_add_folder.png?direct&600 |}}
+  - Now that we have our cluster of Syncthing nodes, we can configure the folders that need to be synchronized across them. In our example here, we want to synchronize the games save files in ''/userdata/saves/''. Be mindful of the ''folderID'' that is provided here. I kept the default one assigned by Synchthing, but you can put your own. What is important is that you keep the same ''folderID'' for all nodes in the cluster.\\ {{::syncthing_4_add_folder.png?direct&720|}}
+  - 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|}}
-  * Then on the "sharing" tab of the same screen, you can select all the nodes you want to synchronize this Batocera saves folder with.
+  - 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|}}
-{{ ::syncthing_5_sharing_folder.png?direct&600 |}}
+  - 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.
-  * 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.
+</WRAP>
-{{ ::syncthing_6_shared_folder.png?direct&600 |}}
+  - 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|}}
-  * 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&600 |}}
-  * 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&600 |}}
 ===== Operational running =====
@@ Line 62: / Line 60: @@
   * At any given time, you can check the status of the synchronization across the cluster of Syncthing nodes on any of them with this screen.
 {{ ::syncthing_8_progress_multiple_devices.png?direct&600 |}}
   * Right now, when a new save file is added, or when a save file is updated on a node, you need to "reload gamelists" from the main menu to see the new save files and save screenshots updated in EmulationStation.
@@ Line 71: / Line 68: @@
   * **Open the Syncthing UI in Batocera:** ''%%/usr/bin/syncthing -browser-only%%''
   * **Open the Syncthing command line via SSH:** ''%%/usr/bin/syncthing --gui-address http://0.0.0.0:8384%%''
+  * **Open the Syncthing command line via SSH when ENFORCE SECURITY is enabled:** ''%%/usr/bin/syncthing --gui-address http://127.0.0.1:8384%%''
   * **Run the background service manually:** ''%%/usr/bin/syncthing serve --no-browser --no-restart --logflags=0%%''
+===== Advanced configuration =====
+Syncthing's configuration files are stored at ''/userdata/system/configs/syncthing''.
+===== Troubleshooting =====
+In case something goes wrong with Syncthing, a useful log to check is at ''/userdata/system/logs/syncthing.log''.
+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]].