There’s no way to do it through configuration. You can modify these lines in
PhabricatorDaemonManagementWorkflow if you don’t mind maintaining a small fork:
$daemons = array(
'class' => 'PhabricatorRepositoryPullLocalDaemon',
'label' => 'pull',
'class' => 'PhabricatorTriggerDaemon',
'label' => 'trigger',
'class' => 'PhabricatorFactDaemon',
'label' => 'fact',
'class' => 'PhabricatorTaskmasterDaemon',
'label' => 'task',
'pool' => PhabricatorEnv::getEnvConfig('phd.taskmasters'),
'reserve' => idx($options, 'reserve', 0),
Very old versions of Phabricator supported direct configuration of which daemons should launch, but this was a source of confusion and almost never had legitimate use cases so it was removed years ago to simplify things.
After upcoming changes in https://secure.phabricator.com/T13561 you will likely be able to implement this kind of task without implementing a separate daemon (instead, you could implement a task generator which generates a new task once every hour).
Today, you can sort of accomplish this by either implementing a
GarbageCollector that just runs a periodic task, or by attaching a
WorkerTrigger with an hourly
PhabricatorMetronomicTriggerClock to some application object, but both of these approaches are probably quite a bit messier than implementing a daemon.