Option to activate or deactivate the background fetching
This commit is contained in:
parent
f7ec8d5b8e
commit
81b244f91e
2 changed files with 7 additions and 3 deletions
|
@ -340,7 +340,7 @@ class Processor
|
|||
}
|
||||
}
|
||||
|
||||
if ($fetch_by_worker) {
|
||||
if ($fetch_by_worker && DI::config()->get('system', 'fetch_by_worker')) {
|
||||
Logger::notice('Fetching is done by worker.', ['parent' => $activity['reply-to-id'], 'recursion-depth' => $recursion_depth]);
|
||||
$activity['recursion-depth'] = 0;
|
||||
if (!Fetch::hasWorker($activity['reply-to-id'])) {
|
||||
|
|
|
@ -282,6 +282,10 @@ return [
|
|||
// Priority for the expirary notification
|
||||
'expire-notify-priority' => PRIORITY_LOW,
|
||||
|
||||
// fetch_by_worker (Boolean)
|
||||
// Fetch missing posts via a background process
|
||||
'fetch_by_worker' => false,
|
||||
|
||||
// free_crawls (Integer)
|
||||
// Number of "free" searches when system => permit_crawling is enabled.
|
||||
'free_crawls' => 10,
|
||||
|
@ -421,8 +425,8 @@ return [
|
|||
'max_processes_frontend' => 20,
|
||||
|
||||
// max_recursion_depth (Integer)
|
||||
// Maximum recursion depth when fetching posts until the job is delegated to a worker task.
|
||||
'max_recursion_depth' => 10,
|
||||
// Maximum recursion depth when fetching posts until the job is delegated to a worker task or finished.
|
||||
'max_recursion_depth' => 50,
|
||||
|
||||
// maximagesize (Integer)
|
||||
// Maximum size in bytes of an uploaded photo.
|
||||
|
|
Loading…
Reference in a new issue