
- #Syncthing without homegroup install#
- #Syncthing without homegroup manual#
- #Syncthing without homegroup android#
Syncthing Autostartįor a desktop, add to Startup Applications /usr/bin/syncthing -no-browser -home="/home/user/.config/syncthing"įor a server, create a service, or something like that. For example, a large repository can be synchronized between two larger-capacity devices (e.g, Debian server and Debian workstation), but also allow access via SFTP for smaller-capacity devices (ChromeOS/Android). Synchronization is useful, but is not a replacement for SFTP which should be seen as on-demand push/pull.
#Syncthing without homegroup manual#
It is important to have a manual workflow as well (or semi-automated) so that things are easier to manage. That server folder can have SFTP for remote access and also provide two-way synchronization back to the desktop for things such as editing images that are on a web server. On desktop, move images to a second folder (removing them from mobile via synchronization), and then have the second folder synchronized to a server.
:max_bytes(150000):strip_icc()/AquaHomeGroup15StageShowerFilter-b32e8a0380f04124bbeda369463acc41.jpg)

Images/Photos folder on a mobile device.The best approach is to partition into folders so that different folders contain different content that will be sychronized differently. Other files one will want only in one or two locations (large files/repositories). Some files one will want to keep everywhere, with version control. One-way synchronization, two-way sinchronization, master and slave device replication, etc. The main thing is to think out one's synchronization policies and plans.
#Syncthing without homegroup android#
The Android syncthing app has a toggle to support auto-on functionality as needed. See also Starting Syncthing Automatically Menu > Preferences > Default Applications for LXSession > -no-browser.Configure Syncthing to Turn on Automaticallyįor Debian/LXDE the simple approach is to add an item to the autostart menu Note that this is the same directory that is used in ChromeOS for inbound, two-way shares. Note that the best approach is then a manual copy/paste of the images to a better archived directory structure that is then synced to a backup server, and a manual image deletion on the Android device, on a monthly basis.įor an inbound, two-way sync to the Android device for critical (editable) files, the directory is: /storage/emulated/0/Download. Note that the best approach is to share out something like /syncthing-photos as a one-way share, and root that to the photos directory (either the local device or MicroSD card), and then also create an inbound two-way sync for a subset of critical documents.įor devices with more storage, additional inbound two-way shares could be added to provide greater access to one's documents.įor example on an Android device with a MicroSD card, the photos are shared under /storage/CE6A-1402/DCIM/Camera.
#Syncthing without homegroup install#
Had to punch holes through lightsail networking and also add rules for UFWįor Android and ChromeOS devices, install Syncthing for Android from the Play Store.

xml file sudo nano ~/.config/syncthing/config.xmlĬhange the 127.0.0.1 address to 0.0.0.0 to enable access from anywhere Allow Ports on Debian Install syncthing sudo apt install syncthingĮdit the. Note: for Debian testing there is no need to add a repository.Īdd PGP key curl -s | sudo apt-key add -Īdd the "stable" channel to your APT sources: echo "deb syncthing stable" | sudo tee /etc/apt//syncthing.list There is also an Android app, so that is what will be used on Android and ChromeOS. There are ports and other configuration issues to enable for routing. Syncthing is available from repositories and directly from Github. Syncthing versioning doesn't really work as expected by the name, so that is really backup-very-lite.

Real World Replacement of Dropbox Syncthing for File Synchronizationįile synchronization is not backup, though with versioning there is a sort of backup-lite going on.
