You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 4, 2021. It is now read-only.
Hi,
I have a couple of million previews generated in nextclouds cache which causes the find command at boot of container to take atleast 20 minutes to finish.
I am talking about this one:
find /data ! -user 1000 -o ! -group 1000
it would be nice if we could exclude the preview folder or something.
Or maybe only run this command if the container is new. If I reboot my machine, nextcloud is down for a long time. So I always need to remember to kill the find command.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I have a couple of million previews generated in nextclouds cache which causes the find command at boot of container to take atleast 20 minutes to finish.
I am talking about this one:
it would be nice if we could exclude the preview folder or something.
Or maybe only run this command if the container is new. If I reboot my machine, nextcloud is down for a long time. So I always need to remember to kill the find command.
The text was updated successfully, but these errors were encountered: