This release addresses the following issues:
Include the previous release note below for your convenience.
[!WARNING]
1. Underlying API changes
Please ensure your mobile app and server are on the same version. Otherwise, you won't be able to access the app.
We advise you to wait for the mobile app to be reviewed and released from the app stores before updating your instance to avoid disrupting your users.
2. Environment variables
SERVER_PORT,MICROSERVICES_PORT, andMACHINE_LEARNING_PORTwere renamed toIMMICH_PORTHOSTandMACHINE_LEARNING_HOSTwere renamed toIMMICH_HOST3. Removal of the
immich-microservicescontainerThe microservices container/process can now be deployed within the immich-server container itself and is done so by default.
Please refer to our documentation for a detailed explanation of this change and a way to keep microservices as a separate container.
Please edit your
docker-compose.ymlfile with the following changes. If you use hardware acceleration previously inimmich-microservices, you can move theextendsblock's content to theimmich-serverservice to keep the same functionality.When you bring the container up, please make sure to include the
--remove-orphansflag, so that theimmich-microservicescontainer is removed properly. So the full command will bedocker compose up -d --remove-orphans
services:
immich-server:
container_name: immich_server
image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
- command: ['start.sh', 'immich']
volumes:
- ${UPLOAD_LOCATION}:/usr/src/app/upload
- /etc/localtime:/etc/localtime:ro
env_file:
- .env
ports:
- 2283:3001
depends_on:
- redis
- database
restart: always
- immich-microservices:
- container_name: immich_microservices
- image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
- # extends: # uncomment this section for hardware acceleration - see https://immich.app/docs/features/hardware-transcoding
- # file: hwaccel.transcoding.yml
- # service: cpu # set to one of [nvenc, quicksync, rkmpp, vaapi, vaapi-wsl] for accelerated transcoding
- command: ['start.sh', 'microservices']
- volumes:
- - ${UPLOAD_LOCATION}:/usr/src/app/upload
- - /etc/localtime:/etc/localtime:ro
- env_file:
- - .env
- depends_on:
- - redis
- - database
- restart: always
Welcome to release v1.106.0 of Immich. Woooh, this release is packed with many new features, improvements, and bug fixes. This is one of the longest release stretches we have ever done, with over 230 closed PRs over a month. I hope you enjoy this release as much as we do, and we have more brewing on the horizon; let's go over some of the highlights of the release below:
immich-microservices containerimmich-microservices container"microservices be gone" - Zack
Actually, it is still there but in a true microservices manner where we spawn it in a separate process. Woohoo, one more container down to simplify the official setup of Immich!
This change is one of many pieces of upcoming work to change how we handle jobs. Microservices were always a patch for the problem that we couldn't run background tasks within the main server, which would introduce contention for the API itself. Using workers, we can now have these within the same container, separated into different V8 engines. Moving forward, we will be looking to split out "microservices" into actual microservices such as transcoding, thumbnails, etc., allowing such things as distributing transcoding alone to another instance.
The immich-server container contains multiple workers:
api: responds to API requests for data and files for the web and mobile app.microservices: handles most other work, such as thumbnail generation and video encoding, in the form of jobs. Simply put, a job is a request to process data in the background.If you prefer to throttle or distribute the workers, you can use the environment variables to specify which container should pick up which tasks.
For example, for a simple setup with one container for the Web/API and one for all other microservices, you can do the following:
Copy the entire immich-server block as a new service and make the following changes to the copy:
- immich-server:
- container_name: immich_server
...
- ports:
- - 2283:3001
+ immich-microservices:
+ container_name: immich_microservices
Once you have two copies of the immich-server service, make the following changes to each one. This will allow one container only to serve the web UI and API and the other one to handle all other tasks.
services:
immich-server:
...
+ environment:
+ IMMICH_WORKERS_INCLUDE: 'api'
immich-microservices:
...
+ environment:
+ IMMICH_WORKERS_EXCLUDE: 'api'
This release adds the much-anticipated ability to detect duplicate assets that aren't exactly identical, whether because of a difference in resolution, compression or metadata. To give you control over which asset(s) to keep, the assets aren't deduplicated immediately. Instead, there's a new Duplicates page where you can review duplicates to keep or trash them. An asset with the largest file size is selected by default.
https://github.com/immich-app/immich/assets/27055614/70c7a997-96e5-43ba-8d03-03c30559189c
To get started, you can run the new duplicate detection job on all assets. You won't need to do this for new assets, as they'll be automatically processed.
The Duplicates page is under a new Utilities section in the sidebar. Stay tuned for other features that will go into this section!
Until now, hardware acceleration for most backends only applied to encoding; decoding and tone-mapping were still done on the CPU. There's now an opt-in hardware decoding toggle that allows you to accelerate the full transcoding process for NVENC, QSV, and RKMPP. Some testing showed a 10x speed improvement compared to accelerated encoding alone (results are subject to your hardware and the video itself, of course).
Keep in mind that hardware and video compatibility becomes more relevant with this setting, which is why it's currently opt-in.
Special thanks to Jellyfin's @nyanmisaka for their helpful tips and suggestions for this feature!
Immich now tries to find a descriptive video thumbnail instead of simply using the first frame. No more black images for thumbnails!
Before:
After:
This change won't apply retroactively to existing videos. To update video thumbnails, you can either select them and choose Refresh Thumbnails from the overflow menu or re-run thumbnail generation on all assets through the job panel to update all of them.
Two new event types have been added for which email notifications can be sent out:
Also, users can now control their notification settings for each event. Notification preferences can be viewed on the web account settings page.
We have added translation for Immich on the web. You can help us translate the web to your native language by accessing our Weblate project here.
You can change the app to your language from the Account Settings > App Settings > Language
<!-- Release notes generated using configuration in .github/release.yml at main -->
Full Changelog: https://github.com/immich-app/immich/compare/v1.106.2...