Syncthing Server - Revision history

ToroidalCore at 20:07, 12 September 2020

2020-09-12T20:07:13Z

← Older revision		Revision as of 20:07, 12 September 2020
Line 17:		Line 17:
	ssh -L 7000:localhost:8384 servername		ssh -L 7000:localhost:8384 servername

	That forwards the GUI, which is running on port 8384 on the server, to port 7000 on your local machine. I chose port 7000 since I was already running Syncthing on my local machine. When you log in just run <code>syncthing</code> at the command line to get it started. Then, in a web browser, just connect to <code>http://localhost:7000</code> on your machine. Reconfiguring Syncthing to listen to the whole network and not just on localhost is another option, but a little less secure.		That forwards the GUI, which is running on port 8384 on the server, to port 7000 on your local machine. I chose port 7000 since I was already running Syncthing on my local machine. When you log in just run <code>syncthing</code> at the command line to get it started. Then, in a web browser, just connect to <code>http://localhost:7000</code> on your machine. Reconfiguring Syncthing to listen to the whole network and not just on localhost is another option, but a little less secure. I recommend setting up a username and password for the GUI, even if you only have it listen on localhost.

	~~I configured the directories~~ to sync ~~to point to an external hard drive;~~ on ~~my laptops and desktop I just have~~ the folders in ~~my home directory~~. ~~From then on~~, ~~directories on your computers should sync as long as you allow them to be shared~~ in the ~~GUI; make sure~~ the ~~Folder IDs are the same~~.		If you have multiple users who want to sync on your server, they'll each need their own instance. In that case, change the GUI port each listens on so there are no conflicts.

			Starting it for the first time gets the initial configuration going. Before configuring any shared folders I set it up to autostart (next section), otherwise you need to leave Syncthing running in your SSH session. After you start it and confirm you can connect, hit <code>Ctrl C</code> in the terminal to stop the server and move on.

	=== Starting the Server ===		=== Starting the Server ===
Line 35:		Line 37:

	systemctl --user status syncthing.service		systemctl --user status syncthing.service

			At this point Syncthing should start as your user on boot. When this is configured, SSH in as above and set up folders to sync. In the case of the NAS, I chose to locate the synced folders on an external hard drive, and not my home directory (which is on a CF card). On my desktop and laptops, the synced folders are all in my home directory.

ToroidalCore at 20:00, 12 September 2020

2020-09-12T20:00:08Z

← Older revision		Revision as of 20:00, 12 September 2020
Line 9:		Line 9:
	Syncthing can run just fine on a headless machine, with a caveat - each user requires a running instance. (This is the case as far as I know, I don't know if a multiuser version is in the works at the moment.) Also, on my laptops and desktop, I start it with my desktop environment, whereas my server doesn't have a GUI installed. I'd like it to start up on boot, but running as my user.		Syncthing can run just fine on a headless machine, with a caveat - each user requires a running instance. (This is the case as far as I know, I don't know if a multiuser version is in the works at the moment.) Also, on my laptops and desktop, I start it with my desktop environment, whereas my server doesn't have a GUI installed. I'd like it to start up on boot, but running as my user.

	~~These instructions are from the [https://docs.syncthing.net/users/autostart.html#linux Syncthing documentation] for autostarting on Linux.~~ I'm running this on Debian 10 on a single board computer (PC Engines Alix, an i386 board), but it should work on a Raspberry Pi as well. In fact, with a Pi 3 or 4, it would probably run better.		I'm running this on Debian 10 on a single board computer (PC Engines Alix, an i386 board), but it should work on a Raspberry Pi as well. In fact, with a Pi 3 or 4, it would probably run better.

			=== Configuring Syncthing ===

	The first thing to do is to actually configure Syncthing. This is based on the [https://docs.syncthing.net/intro/getting-started.html Getting Started] page in the docs, which covers things pretty well. However, since this is a headless server, you can use SSH to forward the GUI to your local machine:		The first thing to do is to actually configure Syncthing. This is based on the [https://docs.syncthing.net/intro/getting-started.html Getting Started] page in the docs, which covers things pretty well. However, since this is a headless server, you can use SSH to forward the GUI to your local machine:
Line 15:		Line 17:
	ssh -L 7000:localhost:8384 servername		ssh -L 7000:localhost:8384 servername

	That forwards the GUI, which is running on port 8384 on the server, to port 7000 on your local machine. I chose port 7000 since I was already running Syncthing on my local machine. Then, in a web browser, just connect to <code>http://localhost:7000</code> on your machine.		That forwards the GUI, which is running on port 8384 on the server, to port 7000 on your local machine. I chose port 7000 since I was already running Syncthing on my local machine. When you log in just run <code>syncthing</code> at the command line to get it started. Then, in a web browser, just connect to <code>http://localhost:7000</code> on your machine. Reconfiguring Syncthing to listen to the whole network and not just on localhost is another option, but a little less secure.

			I configured the directories to sync to point to an external hard drive; on my laptops and desktop I just have the folders in my home directory. From then on, directories on your computers should sync as long as you allow them to be shared in the GUI; make sure the Folder IDs are the same.

	~~I configured~~ the ~~directories to sync to point to an external hard drive; on my laptops and desktop I just have the folders in my home directory.~~		=== Starting the Server ===

	Basically, I'm using a systemd unit file to start as a normal user. There should be one with syncthing when you installed it; I found it in <code>/usr/lib/systemd/user/</code>. Copy it to your home directory like this, where <code>user</code> is your username:		These instructions are from the [https://docs.syncthing.net/users/autostart.html#linux Syncthing documentation] for autostarting on Linux. Basically, I'm using a systemd unit file to start as a normal user. There should be one with syncthing when you installed it; I found it in <code>/usr/lib/systemd/user/</code>. Copy it to your home directory like this, where <code>user</code> is your username:

	cp /usr/lib/systemd/user/syncthing.service /home/user/.config/systemd/user/		cp /usr/lib/systemd/user/syncthing.service /home/user/.config/systemd/user/

ToroidalCore at 19:43, 12 September 2020

2020-09-12T19:43:27Z

@@ Line 9: / Line 9: @@
 Syncthing can run just fine on a headless machine, with a caveat - each user requires a running instance.  (This is the case as far as I know, I don't know if a multiuser version is in the works at the moment.)  Also, on my laptops and desktop, I start it with my desktop environment, whereas my server doesn't have a GUI installed.  I'd like it to start up on boot, but running as my user.
-These instructions are from the [https://docs.syncthing.net/users/autostart.html#linux Syncthing documentation] for autostarting on Linux.  I'm running this on Debian 10 on a single board computer (PC Engines Alix, an i386 board), but it should work on a Raspberry Pi as well.  In fact, with a Pi 3 or 4, it would probably run better.  I'm assuming you have it running and configured on one or more client machines as well.
+These instructions are from the [https://docs.syncthing.net/users/autostart.html#linux Syncthing documentation] for autostarting on Linux.  I'm running this on Debian 10 on a single board computer (PC Engines Alix, an i386 board), but it should work on a Raspberry Pi as well.  In fact, with a Pi 3 or 4, it would probably run better.
 Basically, I'm using a systemd unit file to start as a normal user.  There should be one with syncthing when you installed it; I found it in <code>/usr/lib/systemd/user/</code>.  Copy it to your home directory like this, where <code>user</code> is your username:
@@ Line 19: / Line 27: @@
   systemctl enable syncthing@user.service
   systemctl start syncthing@user.service

ToroidalCore at 19:36, 12 September 2020

2020-09-12T19:36:37Z

@@ Line 1: / Line 1: @@
-[https://syncthing.net/ Syncthing] is a tool written in Go to keep files synchronised between computers.  It's decentralized, meaning instead of syncing to a server, your computers can find each other on the network and sync amongst themselves.  It can work over the internet as well, although I don't use it that way.
+[https://syncthing.net/ Syncthing] is a tool written in Go to keep files synchronised between computers.  It's decentralized, meaning instead of syncing to a server, your computers can find each other on the network and sync amongst themselves.  While I don't use it outside of my home network, it can run over the internet as well - it uses relay and discovery severs, and can even traverse NAT.
-Prior to Syncthing, I used [https://nextcloud.com/ NextCloud], which runs on a web server.  I used this to keep some directories on several computers in my home network synchronized.  It worked, and I actually still have an install I point my phone too (although Syncthing has an Android app as well).  However, sometimes it would be slow, particularly with a lot of small files.  The server also stores all of its files in its own directory, and depends on a database (I have used both MariaDB and SQLite).
+Prior to Syncthing, I used [https://nextcloud.com/ NextCloud], which runs on a web server.  I used this to keep some directories on several computers in my home network synchronized.  It worked, and I actually still have an install I point my phone too (although Syncthing has an Android app as well).  However, sometimes it would be slow, particularly with a lot of small files.  The server also stores all of its files in its own directory, and depends on a database (I have used both MariaDB and SQLite), as opposed to Syncthing which is just its own executable.
-While I like the idea of not having to have a dedicated server in the sense of NextCloud, I do have a NAS I would like to keep the directories I sync on.
+One advantage of the central model NextCloud uses is that if you only have one of the computers you're syncing online, it can still keep the copy of the server up to date.  While Syncthing can deal with conflicts (by renaming the conflicting files), it's nice to not have to have both machines on for them to sync in all cases.  (Although again, Syncthing can sync the two if only the two of them are online; NextCloud would still need to talk to its server.)  I had already had a machine running with an external hard drive as kind of a stopgap NAS, so I looked into how to get Syncthing going on this as well.

ToroidalCore: Created page with "[https://syncthing.net/ Syncthing] is a tool written in Go to keep files synchronised between computers. It's decentralized, meaning instead of syncing to a server, your comp..."

2020-09-11T03:02:58Z

Created page with "[https://syncthing.net/ Syncthing] is a tool written in Go to keep files synchronised between computers. It's decentralized, meaning instead of syncing to a server, your comp..."

New page

[https://syncthing.net/ Syncthing] is a tool written in Go to keep files synchronised between computers. It's decentralized, meaning instead of syncing to a server, your computers can find each other on the network and sync amongst themselves. It can work over the internet as well, although I don't use it that way.

Prior to Syncthing, I used [https://nextcloud.com/ NextCloud], which runs on a web server. I used this to keep some directories on several computers in my home network synchronized. It worked, and I actually still have an install I point my phone too (although Syncthing has an Android app as well). However, sometimes it would be slow, particularly with a lot of small files. The server also stores all of its files in its own directory, and depends on a database (I have used both MariaDB and SQLite).

While I like the idea of not having to have a dedicated server in the sense of NextCloud, I do have a NAS I would like to keep the directories I sync on.