FEEDBACK WANTED: Insync 3 headless

Continuing the discussion from FEEDBACK WANTED: Insync 3 headless:

  1. Why do you need Insync headless?
    Because I can run batch jobs on an unattended machine.

  2. What is your workaround without Insync headless?
    At the moment, I’m using an older version. Works fine, BTW.

  3. What features/behavior would make Insync 3 headless better than Insync 1.5 headless?
    Being supported is more than enough!

  4. Would you prefer to have Insync 3 headless as a separate product or integrated into the GUI?
    Don’t care but being integrated could lead to installation problems… (e.g. libraries compatibility)

  5. What platform(s) do you need Insync headless to work?
    Linux. Maybe useful for MacOS, I don’t know. Useless for windoze.

  • Why do you need Insync headless?
    My use case revolves around being able to have workflows that are downstream of Google Drive files. I have a NAS server (Ubuntu) which I run and I use Google Drive as backup/pipeline solution. It’s a bit difficult to explain but as it stands, I have to have a GUI installed on that machine just for Insync. The problem is that every time I run into an error (what prompted this is that I’m getting an OS Error because one of my drives is full. The GUI fails silently and I had to physically walk into that room, connect a monitor, poke around etc. instead of being able to connect over a terminal like I normally do).

  • What is your workaround without Insync headless?
    Install a distribution with a GUI solely to use Insync.

  • What features/behavior would make Insync 3 headless better than Insync 1.5 headless?
    I didn’t use Insync 1.5 headless, I must have purchased after that was deprecated.

  • Would you prefer to have Insync 3 headless as a separate product or integrated into the GUI?
    It might be nice if it was a separate product that was integrated with the GUI application. E.g. you could run the GUI if you had it on a machine but it still let you alter your settings from the command line. So on the machine I have it on now, I have a GUI so I could configure it that way but if I had an issue or wanted to change settings, I could SSH in. That would be in contrast to installing a separate product that I would have to use one or the other. That said, I would be fine with that approach as well.

  • What platform(s) do you need Insync headless to work?
    Linux (Ubuntu)

1.5 headless is not deprecated and is the one we recommend you use for now

  1. Backup personal gdrive on headless home server.
  2. Rclone. Works well enough, but have encountered incompatibilities between insync and rclone conversion of Google Docs to MS Office format, so it’s better to use the same product for desktop and server sync.
  3. Regular security updates and bug fixes would be a good thing.
  4. If the gui and headless functionality could be integrated, that would be good: but I could live with them remaining separate products.
  5. Linux: Latest Ubuntu LTS, CentOS release, Fedora.
  1. Syncing my Windows Subsystem for *nix Profile between Workstations.
  2. Currently I can do this using the windows Version of it, but Problem is Permissions get f*ed up each time it needs to update something. Don’t sync certain files that get executed automatically, on startup to reset the current Permissions.
  • Why do you need Insync headless?

Because I automate everything in my workstation, including initial setup with Ansible. Plus, I generally prefer setting up stuff with cli, which is extensible for automation.

  • What is your workaround without Insync headless?

Well, none!

  • What features/behavior would make Insync 3 headless better than Insync 1.5 headless?

I haven’t checked 1.5 headless features, but I would need a systemd service launched at statup with --user option.

  • Would you prefer to have Insync 3 headless as a separate product or integrated into the GUI?

Separate, I guess. The client / daemon architecture would fit nicely, with headless being just a second client. You would have an insyncd daemon launched by systemd in user land, an insync-headless to interact with the daemon through cli, and insync-gui or insync the GUI program.

  • What platform(s) do you need Insync headless to work

Mainly Arch and Debian. Perhaps MacOs.