v1.52.0 #2110
Replies: 3 comments 7 replies
-
Can you please provide an example how to separate thumbnails, encoded videos and profile picture? I mean the docker-compose example. Currently there is only one volume for photos location. |
Beta Was this translation helpful? Give feedback.
-
Something like this should work: You should add the new volumes to the You do not have to use an env variable on the left either, so you could do something like this as well: The left side is the location of thumbs, encoded-video, etc. The right side should point to these internal paths in the container:
You can configure all or just some of the volumes, as needed. Volumes should only be needed (in addition to |
Beta Was this translation helpful? Give feedback.
-
It seems that my Docker doesn't support nested subdirectory mount. So I mounted them seperatedly rather than just override the thumbs folder. .env
docker-compose.yml, in
|
Beta Was this translation helpful? Give feedback.
-
v1.52.0
Highlights
This release includes many bug fixes and hardening of the recent new features in Immich. We are making Immich more robust as we try to move into the stable territory of the application. I hope you enjoy this release.
Splitting generated content into a separate folder
This is a feature to build toward a custom location setting for generated files so that the user can leverage SSD for quick serving of thumbnails and encoded video and put the original files to HDD. Users can now store thumbnails and encoded videos at a different location. The separation between generated content and originals makes it easier to know what to backup. It's more clear what folder media is uploaded. Accomplished by swapping
type/uuid
touuid/type
.The resulting folder structure is as follows:
library/<uuid>/<template>
profile/<uuid>
thumbs/<uuid>
encoded-videos/<uuid>
Migration Notes:
library/
<uuid>/thumbs
) - regenerates thumbs inthumbs/
<uuid>/encoded-videos
) - regenerates encoded videos inencoded-videos/
<uuid>/profile
) - moves profile image toprofile/
Hardening mobile synchronization mechanism
We've solved issues with concurrency that caused the mismatch in the sync status of the local vs. remote assets on the mobile app and further optimized the
Asset
model to guard against bad upload cases from the CLI. The sync and display on the mobile app should now correctly display all local and remote assets.Update search UI
Searching is now CLIP-enabled by default. You can search for asset metadata such as location info, camera model.etc by prepending
m:
to your search term, for example,m:Long Beach
.On the web, we also added the search history (maximum of 5) to the search bar for a better search experience.
We revamped the Search page on the mobile app to include the new search mechanism and the metadata/CLIP search similar to the web.
As always, please consider supporting the project.
🎉 Cheer! 🎉
Support
If you find the project helpful and it helps you in some ways, you can support the project one time or monthly from GitHub Sponsors
It is a great way to let me know that you want me to continue developing and working on this project for years to come.
What's Changed
Server
Mobile
Web
Others
New Contributors
Full Changelog: https://github.com/immich-app/immich/compare/v1.51.2...
This discussion was created from the release v1.52.0.
Beta Was this translation helpful? Give feedback.
All reactions