Dynamic quota workaround in SSO configuration
Short version:
I'd like to separate the uploads in library/username to different zfs datavols per-user to keep an eye on single space usage.
Hi!
I am working to roll out Immich for my family and friends to give them an alternative to google photos et similar,
I've managed to integrate Immich with Authelia (LLDAP as ldap server) (https://www.authelia.com/integration/openid-connect/clients/immich/) and can log as my ldap users without issues,
I've also managed to get the quota attribute to work from ldap but read that it get read only on user creation, so I won't be able to modify it further. (https://docs.immich.app/administration/oauth/)
I've looked into Storage Templates but it does not help my case.
I've tried to create a ZFS Datavol per-user and assigning it to the library/user folder but I've seen that if Immich finds the folder before the user creation it removes that folder and re-creates it, so this approach is a no-go.
I was wondering if ther might be something I did not think about.
I can fallback to create a single ZFS datavol for all immich uploads and the manage the space used by each user in another way.
thank you very much
I am on dockerized immich v2.3.1,
in my docker compose I've set the storage like this:
volumes:
- ${UPLOAD_LOCATION}:/data
and in my .env:
UPLOAD_LOCATION=/data/auth/immich_upload
I'd like to separate the uploads in library/username to different zfs datavols per-user to keep an eye on single space usage.
Hi!
I am working to roll out Immich for my family and friends to give them an alternative to google photos et similar,
I've managed to integrate Immich with Authelia (LLDAP as ldap server) (https://www.authelia.com/integration/openid-connect/clients/immich/) and can log as my ldap users without issues,
I've also managed to get the quota attribute to work from ldap but read that it get read only on user creation, so I won't be able to modify it further. (https://docs.immich.app/administration/oauth/)
I've looked into Storage Templates but it does not help my case.
I've tried to create a ZFS Datavol per-user and assigning it to the library/user folder but I've seen that if Immich finds the folder before the user creation it removes that folder and re-creates it, so this approach is a no-go.
I was wondering if ther might be something I did not think about.
I can fallback to create a single ZFS datavol for all immich uploads and the manage the space used by each user in another way.
thank you very much
I am on dockerized immich v2.3.1,
in my docker compose I've set the storage like this:
volumes:
- ${UPLOAD_LOCATION}:/data
and in my .env:
UPLOAD_LOCATION=/data/auth/immich_upload
