instead of looping trough all users and seeing if they have unscanned files, we do a single query to find all storages that need scanning and run trough the users for them
Signed-off-by: Robin Appelman <robin@icewind.nl>
To continue this formatting madness, here's a tiny patch that adds
unified formatting for control structures like if and loops as well as
classes, their methods and anonymous functions. This basically forces
the constructs to start on the same line. This is not exactly what PSR2
wants, but I think we can have a few exceptions with "our" style. The
starting of braces on the same line is pracrically standard for our
code.
This also removes and empty lines from method/function bodies at the
beginning and end.
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
This job can be initiated by a user to transfer a file/folder to a
target user.
The target user will have to accept the job.
Once that is done the transfers is initiated in the background.
Both parties get notified when the job is done.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
when using (only) object store this job doesn't do any scanning anyway,
but all the setup can still be expensive on large setups
Signed-off-by: Robin Appelman <robin@icewind.nl>