Replies: 3 comments 1 reply
-
Correct
Immich will not realise the files were moved, and all kinds of stuff will break when it fails to find them where it expects. There is no recommended approach for this. You'll probably need to copy the files and then manually delete the internal library ones via the Immich GUI. |
Beta Was this translation helpful? Give feedback.
-
There's an idea, not verified but may work: |
Beta Was this translation helpful? Give feedback.
-
I have the same workflow. It would be nice to have a extended delete-function to delete a image from the library and force deleting the file as well. |
Beta Was this translation helpful? Give feedback.
-
I am using Immich already with curated external libraries.
What I would really like to do is to use it for the bulk of images in my (and my spouses) phone, too.
My idea is to let Immich upload the images from the phone into its internal storage so they end up in the timeline (that should work without a problem).
I would like to be able to organize the photos of special interest (e.g. of specific events) into different folders. That should be possible by utilizing Storage Templates and using the album name as a subfolder in the Storage Template.
I would then want to move these folders with that images to an external library.
The one thing I am afraid of is the following note in https://immich.app/docs/administration/backup-and-restore#asset-types-and-storage-locations:
This sounds like moving images from Immichs internal storage to an external library on filesystem level is a bad idea.
But what does actually happen in such a case? What is this warning referring to?
And what is the recommended approach for doing this? How can I move images from the internal storage (that are already visible in the timeline) to a external library?
Beta Was this translation helpful? Give feedback.
All reactions