[Feature] Path per user

[MrSpoocy]

The feature

I am currently moving to Immich with my whole family and my sister has a small child. As a result, she already takes over 40,000 photos and videos. That quickly takes up more than 400GB. When importing, I ran into the problem that my server SSD doesn't have enough space. So I bought a second one. But now you can only put external libraries in another directory and even then, thumbnails and encoded videos are written to the main directory. I think it would be quite useful if we can specify a path per user so that the directory structure changes as follows:

current:

• library
  • encoded-video
    • USER1
    • USER2
  • library
    • USER1
    • USER2
  • thumbs
    • USER1
    • USER2
  • upload
    • USER1
    • USER2

after:

• library
  • USER1
    • encoded-video
    • library
    • thumbs
    • upload
  • USER2
    • encoded-video
    • library
    • thumbs
    • upload

This makes it easy to mount other paths or symlinks. A migration should then not be so difficult. I could also help with the code. But first I wanted to know what you think of the idea.

Platform

• Server
• Web
• Mobile

[aisbergde]

I think this is a good idea. And this is the normal or common way to store data in file system.

External libraries already can be stored in different places and can be mounted to the current internal structure. Maybe the same would be possible for the internal libraries? Then the internal folder structure could stay as it is.

[Samco2005]

I think it's a nice thing to have...

[MrSpoocy]

I've already looked a bit in the code and it looks like this could all be possible with a few changes in server/src/domain/storage/storage.core.ts (for the backend). Of course, something is still needed in the frontend and a migration script.

[Cyanogenbot]

This could be interesting to make interoperability with nextcloud easier aswell!

[jaimetur]

Definitely this is a must. Most of us would like to separate the different user libraries on different folders or even volumes.

One common case is place each user library into /homes/user path, in that way, we can give access to each user to its /homes/user directory and they can see and manage its assets, and what is more important, we can make sure that each user don't exceed the given hard drive quota limit defined in the system