Search code, repositories, users, issues, pull requests...
syncspirit is a continuous file synchronization program, which synchronizes files between devices. It is built using the C++ rotor actor framework. It implements the BEP-protocol for files synchronization, or, simplistically speaking, it is a syncthing-compatible synchronization program at protocol level, which uses the syncthing infrastructure (for global discovery and relaying).
i.e. it records some peer, adds a folder, then shares the folder with the peer device, connects to the peer and downloads all files into /tmp/my_dir/data . The peer device currently can only be syncthing. Then syncspirit either exits after 2 minutes of inactivity or when you press ctrl+c. The output is successful, because I previously authorized this device with the syncthing web interface, and shared the folder with this device (syncspirit).
syncthing is implemented using go programming language, which is a good fit for services. As a result, syncthing itself is written as a web-service, which exposes a REST-API for clients. So, yes, the end-user software should also have a front-end, which is usually web-browser (or embeds web-browser), which is written in different programming language (e.g. javascript or java).
