From 025c4ff1e54a5888395b2f19f5af5134d06d7c09 Mon Sep 17 00:00:00 2001 From: wsw70 <1345886+wsw70@users.noreply.github.com> Date: Fri, 20 Sep 2024 13:26:42 +0200 Subject: [PATCH] Added another scenario for a service-based configuration on Windows --- users/autostart.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/users/autostart.rst b/users/autostart.rst index b7b33139..6a93a981 100644 --- a/users/autostart.rst +++ b/users/autostart.rst @@ -210,9 +210,11 @@ is best to create a service that runs as soon as Windows starts. This can be achieved using NSSM, the "Non-Sucking Service Manager". Note that starting Syncthing on login is the preferred approach for -almost any end-user scenario. The only scenario where running Syncthing -as a service makes sense is for (mostly) headless servers, administered -by a sysadmin who knows enough to understand the security implications. +almost any end-user scenario. The only scenarios where running Syncthing +as a service makes sense are + +- for (mostly) headless servers, administered by a sysadmin who knows enough to understand the security implications +- when a dependency on another service is required (for instance if you want to bind Syncthing exclusively to a Tailscale IP) #. Download and extract `nssm `__ to a folder where it can stay. The NSSM executable performs administration as well as executing as the Windows service so it will need to be kept in a suitable location. #. From an administrator Command Prompt, CD to the NSSM folder and run ``nssm.exe install ``