Using months as unit of the max_password_age seems rather coarse, but if it's good enough for the end users it's good enough for me (don't know to which extent this has already been discussed).

For the final file storage (not the intermediate files used for upload), we'll want a way to associate files with a "Library", which can have different storage backends (local filesystem, s3, ...). Not a blocker for a first step, just so we agree on the direction.

I'm not sure about the permissions model.

Fixed long line

Fixed token revocation + test

Rebased on the laravel v9

Rebased on laravel v9

According to our discussion in jabber the idea was to have the following split:

• Library: Controls where files are stored (so for kolabnow we'd have at least initially a single library for all users). This is not exposed to the user. (An alternative name for this could be "Repository")
• Share: Controls who can see files (and probably maintian other acl's as well). Initially each user would have one share giving him access to his files.

I don't know why this is necessary, but seems reasonable.