manage mutagen daemon lifecycle for coder-desktop-macos

[spikecurtis]

Daemon Lifecycle

• We’ll embed the daemon in Coder Desktop as described in the [mutagen docs.](https://mutagen.io/documentation/introduction/daemon/)
  • We’ll use a data directory under the main Coder Desktop data directory to ensure our instance of mutagen doesn’t interfere with other instances on the system (i.e. directly installed by the end user).
• We’ll use Mutagen’s existing autostart capability if possible, and avoid implementing our own autostart.
  • Technical risk: Support is listed as experimental. If we find problems we should be prepared to roll our own lifecycle management.
  • call mutagen daemon register when first file sync is created
  • call mutagen daemon unregister when last file sync is deleted, or file sync disabled entirely.

[ethanndickson]

We’ll use Mutagen’s existing autostart capability if possible, and avoid implementing our own autostart.

Without forking, we won't be able to use mutagen daemon register in conjunction with MUTAGEN_DATA_DIRECTORY as mutagen reads the environment on start-up, and doesn't persist the configured directory.

To test this, I ran MUTAGEN_DATA_DIRECTORY=($pwd) mutagen daemon register, and made sure ~/.mutagen did not exist. Initially, the pwd was used as the data directory, but on restart ~/.mutagen had been created and was used instead. The mutagen source code backs this up.

The Mac app already has support for launching on login - on app launch we could just spawn the mutagen daemon as a background process using mutagen daemon run (as opposed to start) and manage it ourselves.

[spikecurtis]

Agreed, let's use mutagen daemon run and manage ourselves.