FlexGet can be run in daemon mode, which means it will always run in the background, periodically running tasks on a schedule, or running the tasks initiated by another instance of FlexGet. Also see the daemon CLI documentation.
To launch the FlexGet daemon, use the start command:
^Note: Using the optional -d switch will send the FlexGet daemon to the background. Using --autoreload-config will force config reloads before task execution.^
^Note 2: In earlier versions, use --config-autoreload instead of --autoreload-config^
flexget daemon start [-d, --autoreload-config]
To stop a currently running daemon you can use stop:
flexget daemon stop
To check the status of the flexget daemon you can use status:
flexget daemon status
To have the daemon reload the config file from disk you can use the reload-config command:
flexget daemon reload-config
-dDue to an apparent bug in current versions, the -d command may cause Flexget to start but quit immediately on Mac OSX. There are two work-arounds while the issue is looked into:
-d with &.-d option and without an open Terminal window.If you run flexget execute while a daemon is running, the execution will be sent to the running daemon, and either run immediately, or queued for execution after the current running task has finished. The log results of this execution will be sent back to the calling terminal for viewing as well. This means that if you are running a daemon, you need not worry about concurrent calls of flexget execute having problems due to the lock file.
In order to get the daemon to start automatically on system boot, see here.
The scheduler plugin is responsible for executing your tasks periodically. By default it will run all tasks once an hour when FlexGet is running in daemon mode. Please see the scheduler documentation for more information on setting up schedules.