SYNCTHING SETUP INSTALL
SYNCTHING SETUP UPDATE

SYNCTHING SETUP INSTALL

To fix this, you can install a valid certificate. Also, if your server’s domain uses HSTS, the browser will refuse to load the page if using the domain name (accessing IP address will work). The server uses a self-signed certificate which will show an error in your browser. config/syncthing/config.xml and in the gui enabled section, change the address value from 127.0.0.1:8384 to :8384 to tell the server to listen on all interfaces. Run syncthing in the terminal to start the application.īy default, the web interface is only accessible on the machine running Syncthing, so either forward the port through SSH or edit the configuration to allow remote access to the web interface.

SYNCTHING SETUP UPDATE

# HTTPS transport package must be installed first to allow apt update to scan the Syncthing source & recognize the package as an install candidate Theoretically you could run the script on your main computer (or phone if you’re really crazy), but then it has to be on whenever you want to resolve a conflict.# Add the 'stable' channel to your APT sources:Įcho 'deb syncthing stable' | sudo tee /etc/apt//syncthing.list Then in my docker-compose.yaml I mount the directory I want to deconflict to /data in the container: version: '3' The sh-dance at the bottom is probably not necessary, but I used it for debugging and haven’t tested it without it. I use a container and docker-compose because I also run syncthing that way, but you could also use a systemd unit.Īs a brittle but very simple way you could go the nohup/disown route, the main disadvantage being that you have to re-run it after every restart (definitely not recommended, but I ran Minecraft servers like this for quite a while).ĬMD It runs constantly on my server, which also functions as a syncthing node. Makes my life much easier, maybe someone else appreciates. Now instead of sync conflicts/apparent data loss, the worst thing you’ll get is duplicated nodes. The script is running inside the (base of) the Logseq folder.Versioning is enabled (I use staggered versioning).Git is installed on the machine the script runs on.I have been stress testing it a little and it has held up very well. sync-conflict files scattered around the place! Since the sync-conflict files are just normal files that are synced, the conflict resolution can be done on one device and is synced over automatically. Rafael Epplée that automatically detects conflicts and merges the corresponding files.įinally no more.So I built a little script based on Automatically resolve Syncthing conflicts using a three-way merge I don’t always have a perfect internet connection for multiple reasons (German trains, device is off, Wifi is disabled on the E-Reader to save power), so I used to have a lot of conflicts when using Syncthing, which I found super annoying, because often it would look like a data loss (it’s better now that conflict files are shown in Logseq itself, but still annoying) - all the stuff I had written on the train would just be gone.

Syncthing setup