- Why do you need Insync headless?
I sync between my main desktop and laptop when traveling, and when doing so I ssh into my main desktop, and move the files I need to my insync directory. Previously this wasn’t an issue because I could just use the command line interface to start insync on my main desktop remotely via SSH. Now I can’t do that and it’s a PITA to have to start up a VNC session just to start insync. Also, as you may or may not remember, there was an issue with insync not starting with Fedora 30. The workaround was to add a statement at system startup to start insync headless and use the command line interface. If you don’t have a headless mode, you lose a potential circumvention for GUI issues. And, this issue wasn’t fixed quickly - which highlights the need for a command line interface if for nothing else, circumvention purposes. - What is your workaround without Insync headless?
The workaround is to use VNC for file transfer. However, there is no solution if for whatever reason the GUI stops working. - What features/behavior would make Insync 3 headless better than Insync 1.5 headless?
I can’t think of any, the commands were fairly comprehensive. You should at least keep functionality parity with 1.5 - why would you have a later release with less functionality? - Would you prefer to have Insync 3 headless as a separate product or integrated into the GUI?
It should be the same product and incorporated into the GUI as it was previously. Again, I don’t understand the strategy of coming out with a later release of something with less functionality. Insync should always have a command line interface. - What platform(s) do you need Insync headless to work
Linux, specifically the current releases of Fedora.
2 Likes