How to run/use the preview generator?

[foxhoundv]

How does one edit the crontab for apps like the preview generator that need a job ran every # of minutes/hours/days?

@szaimen Thanks for referring me here.

[szaimen]

The docu was moved to #2810

[szaimen]

the concurrency of preview generation is limited starting with nc26 to not bring the instance down. So yeah technically the problem that the instance crashes when doing that is solved.

However indeed depending on the hardware and if you scroll fast it might not be the fastest to generate them on the fly.

[JL102]

the concurrency of preview generation is limited starting with nc26 to not bring the instance down. So yeah technically the problem that the instance crashes when doing that is solved.

Hmm. The documentation of previewgenerator isn't super clear to me on what the preview:pre-generate does under the hood. Does it look at a list of currently-unanalyzed files and then process them? If (i'm pulling numbers out of the air here) say, the max number of images it can process is 10, and there are 50 new images that need to be processed, will the preview:pre-generate job simply need to be run multiple times until it gets through the queue? (in this example, if it's set to run every 10 minutes, then would that mean it takes 50 minutes to get through the queue?) - or does it attempt to generate previews for everything whenever it's run?

[szaimen]

Basically the idea is that you run preview:generate-all once which creates previews for all files and then preview:pre-generate in a cronjob which detects changed and added files and generates previews for these.

[hoggatt]

Thank you for the post! This is basically essential for the memories application.

[meichthys]

@szaimen Sorry to resurrect an old thread. Is intended that we use the Docker host's crontab? This doesn't seem ideal since it would break things if the docker containers were moved to a different host. If possible, i would prefer to use a crontab inside the nextcloud container, however i'm not sure if that's supported, or if it would be reasonable to make the crontab persistent when the image is updated.

[philiprenich]

Like @meichthys , I'm curious why this is done on the Docker host and not within a container. I don't know what the lifecycle issue would be of manually editing a crontab in a container that will be updated when new AIO versions are released though. Are there improvements to this process we can make?