Live and recent posts from across the Fediverse tagged #syncthing, aggregated by home.social.
8 node syncthing cluster with public IPs (IPv6 only) and with config fully deployed and templated out with ansible is up and running now. All of the external dependencies (global discovery and such) disabled.
Just need to cleanup that mess of a playbook (but I won't be moving stuff into roles this time, that cause way too much overhead last time considering that I wasn't going to resuse it anyway and that rewriting it custom tailored to the use case is literally easier...)
Home Clouds/NAS sind sicher eine Lösung digitale Dinge souveräner zu verwalten, doch Komplexität, Angriffsfläche und Zugriffsmöglichkeiten bei einschlägigen Anbietern gehen mir doch zu weit.
Meine Lösung für Sync von Kontakten/Kalendern und #backup:
Ein kleiner, sparsamer Pi mit rsync, syncthing, Baikal und Restic, alles lokal und remote gesichert.
Nicht gerade für Anfänger, doch wer meine Doku (md) gut lesen kann, möge es probieren ✊
https://paste.sh/p4SFA54h#5q_ruWaHubblUkUiNrZdkO7H
Zu den Programmen 👇
https://sabre.io/baikal/
https://restic.net/
#didit #dudgemacht #diday #opensource #pi #rsync #keepitsimple #caldav #carddav #restic #baikal #syncthing
I'll probably never stop being surprised by what AI can/cannot do.
like it can look into the source code of #syncthing and rewrite the code to derive the device ID in awk. But it cannot look into the #ansible documentation to see that
> community.general.python_eval('bytes.fromhex')
doesn't exist...
