Description
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.
Metadata
Metadata
Assignees
Labels
No labels