Git Winch has been designed so that people who are not very familiar with Git can also use it. The reason for using Git is because the Git ecology is very robust for both keeping backups as well as for version control.

As Git Winch works with all the popular Git hosts such as Gitlab, Github and Gitea, it would serve our users admirably well. In fact, you can have your own self-hosted version of Gitlab or Gitea, and with just some minor changes in the gitwinch.ini file and the config.txt file, you can easily run a completely private version of Git Winch

Configuring for self-hosted Gitea or Gitlab
will document this soon

Using Syncthing
Syncthing (https://syncthing.net) is also a very powerful peer-to-peer backup and synchronization system. The advantage of using Syncthing is that you do not need an external hosting service – the way you do with Git. However, there are some notable disadvantages (listed below) and hence we recommend Syncthing to be used only in case of a few known individuals working together in an office. We do NOT recommend that you use Syncthing for everyone in the office.

This is how you can setup Syncthing to work with Git Winch
will document this soon

Disadvantages of Syncthing

• There is no commit, push, pull, etc when you work on a folder managed by Syncthing. Whatever that is done on such a folder will get 'synced' to the same folder that is present in other users' respective folder. That means if someon decides to delete a file, then practically immediately the same file would get deleted in others' folders too. (You can mitigate this issue by asking Syncthing to preserve versions)
• It currently does not have an easy way to detect if a sync has got complete in an automatic manner. So one cannot automatically call a build process – something that is easily possible after a git push