Skip to content

Commit 92c74ff

Browse files
Merge branch 'master' into Documentation
2 parents 1c822e3 + 246cc7a commit 92c74ff

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

admin_manual/ai/overview.rst

+7-1
Original file line numberDiff line numberDiff line change
@@ -181,7 +181,7 @@ Improve AI task pickup speed
181181
----------------------------
182182

183183
Most AI tasks will be run as part of the background job system in Nextcloud which only runs jobs every 5 minutes by default.
184-
To pick up scheduled jobs faster you can set up background job workers that process AI tasks as soon as they are scheduled.
184+
To pick up scheduled jobs faster you can set up background job workers inside your Nextcloud main server/container that process AI tasks as soon as they are scheduled.
185185
If the PHP code or the Nextcloud settings values are changed while a worker is running, those changes won't be effective inside the runner. For that reason, the worker needs to be restarted regularly. It is done with a timeout of N seconds which means any changes to the settings or the code will be picked up after N seconds (worst case scenario). This timeout does not, in any way, affect the processing or the timeout of the AI tasks.
186186

187187
Screen or tmux session
@@ -194,6 +194,12 @@ It would be best to run one command per screen session or per tmux window/pane t
194194
195195
set -e; while true; do sudo -u www-data occ background-job:worker -v -t 60 "OC\TaskProcessing\SynchronousBackgroundJob"; done
196196
197+
For Nextcloud-AIO you should use this command on the host server.
198+
199+
.. code-block::
200+
201+
set -e; while true; do docker exec -u www-data -it nextcloud-aio-nextcloud php occ background-job:worker -v -t 60 "OC\TaskProcessing\SynchronousBackgroundJob"; done
202+
197203
You may want to adjust the number of workers and the timeout (in seconds) to your needs.
198204
The logs of the worker can be checked by attaching to the screen or tmux session.
199205

0 commit comments

Comments
 (0)