Glad to see insync headless as a new release. the old 1.x version stopped working for me a long time ago and I’ve been without a sync option for my home server.
So I kicked things off and I’ve got a couple of questions / concerns:
- It doesn’t seem to support symlinks at all. Just gives me errors. Not only that, but if I dismiss all the errors and then restart the insync-headless daemon, all the errors reappear. I’m not sure the best way to support these, but creating a bunch of errors every time the daemon starts seems like a temporary solution in need of a more long term approach. (FYI, the main thing I use this tool for is to backup certain directories (e.g. like an rsync to the cloud). Just skipping the symlinks would be my least favorite option, but would be better than what we have today. A full sync would be nice.
- I’m not sure where all the configuration data is stored. It doesn’t seem to use the standard /etc/* location. There’s some stuff in a sqlite3 db in .config, but it would seem there’s some other config information stored somewhere else (like where are the selective sync settings?).
- My status says to autostart, but it doesn’t seem to work after a server reboot. I have to issue the following command after reboot to make it start “sudo -u bkuser insync-headless start” I’m sure I could hack in an init.d or systemd service file to make this work, but I’d rather not if there is just something I’m missing.
- Is there some sort of subscription that I’m missing here? I’ve had insync for a LONG time (march of 2014). The old headless version worked fine with my subscription. This one seems to indicate that I’m in “Office Trial (expires on March 28, 2021).”
I’ll keep the feedback coming as I try more stuff out…
As for the 4th point, Insync 3.x-headless is now a separate product from Insync 3.x GUI (driven by user feedback when we were collecting data), which further led us to the direction of having a separate subscription. Here is the