It would be very helpful if there were more details on how to use the config file and VERY helpful if the UI generated JSON config instead of whatever format it stores its config in. That way people could set up in the UI and then use that file with whatever other minor tweaks they want as they turn it into an official service on their NAS or PC Also, can you make directory ownership / key tying a little cleaner. While evaluating you first create RW shares and then often end up creating RO to test out that feature for master -> slave sync. However, btsync will happily keep running even if the folder ownership is no longer correct. It took a while to realized this error was in btsync.log Error while adding folder /share/HDA_DATA/test: Destination folder cannot be identified. Would you like to reset ownership? How do you fix that err w/o having to rm -rf the original folder? I removed everything because it was a small test folder, but if there is a better way, include that in the docs
