- [Reference](https://docs.syncthing.net/intro/getting-started.html)
- For windows, just extract directly into the `Program Files` folder
tar -xzf syncthing-linux-amd64-v2.0.13.tar.gz
ssh -L 9999:localhost:8384 staging
ssh -L 9998:localhost:8384 production
ssh -L 9997:localhost:8384 framework
ssh -L 9996:localhost:8484 work_tower_ubuntu
ssh -L 9995:localhost:8484 work_laptop_ubuntu
Add token from 1password to env file
ssh production
sudo mkdir -p /etc/strelaysrv
sudo tee /etc/strelaysrv/strelaysrv.env > /dev/null <<'EOF'
TOKEN=<token here>
EOF
Forward this port to production pi on router: Unify Site Manager -> Dream Machine Pro Max -> Network Tab -> Settings (bottom left) -> Overview -> Port Forwarding
# Relay Port
22067
Run this from a DEV machine
./deploy.sh && ./deploy.sh -t production
Record the produced relay id
ssh production
journalctl --user -u strelaysrv
~/deploy. actions -> settings -> general -> edit folder defaults. This ensures when you share wiki-data it ends up in the ~/deploy folder instead of being dropped in the home dir- Enable NAT traversal # Magic hard to troubleshoot, Grug do not like, host relay instead
- Global Discovery Servers # Why discover when you can just tell stuff where it lives, Public access? Relay, Private access? NAT discover. Done
./deploy.sh && ./deploy.sh -t production
dynamic, relay://frii.day:22067
Config.wtf to ignore patterns for all shared WTF folders. This file is per device since it changes graphics settingsConfig.wtf file since we exclude it from the sync.Folders: Label:
wiki
Id:
uqcfn-ywpmk
Path:
~/deploy/wiki-data
Remote Device → Addresses -> How do I try to reach them?
Sync Protocol Listen Addresses -> How can they try to reach me?
Put a Relay in the middle add to both fields and you have: Sync Protocol Listen Addresses -> syncthing connects to the relay and waits for pairing Remote Device → Addresses -> tell the relay you would like to use it as a connection (thus lets pair)
Restarting syncthing on Windows appears to fix this issue