Hi, I’m the author of STC CLI tool for Syncthing - GitHub - tenox7/stc: Syncthing CLI Tool · GitHub - It supports managing remote nodes via API, but I want to expand it further to automate tasks on remote nodes.
I wanted to do a small survey and see how people typically manage remote nodes? Do you typically use VPN or open port or anything like that?
Thanks!
To get to the GUI, I use port forwarding via ssh.
I use Tailscale. My Syncthing Devices are configured to bind the GUI (and API) to the Tailscale IP address only.
My Syncthing cluster doesn’t require a lot of management. I run a script twice a day that reports whether each Device is up, when it was last seen if it isn’t, and whether all of its folders show Up to Date.
Could you give an outlook of what remote management features you have in mind? And how that is not covered by the Syncthing internal CLI? The biggest difference I remember is stc being easier to use for some actions, while built-in CLI is more feature-complete.
Primarily SSH port forwarding, but also open port for limited use cases (access control via firewall rules).
In my setup, STC CLI serves double-duty…
It’s accessible via web request to provide a simple lightweight text-based dashboard using a modern web browser, a text-based web browser, cURL and many other tools.
The same web UI is also being parsed by a remote monitoring system. One big plus is that no API key for Syncthing is required and access is read-only. For what I’m interested in, I didn’t need to directly parse JSON from Syncthing’s REST and EVENT APIs.
I use remote.it to administer remote nodes (on which Synthing is only a small part). This gives me a local browser, so I’ve been using the Syncthing web gui that way.
I am always interested in command line tools though, it’s my preferred way of managing things.