ImmichI
Immich•5mo ago
pyromonkey007

v1.136.0 Breaking change upgrade

I've currently got v1.135.3 running and am looking to upgrade to v1.136.0.

Before proceeding I want to confirm if I need to perform the breaking change migration steps for my case or not.

My compose file and .env files are as follows, and don't utilize the IMMICH_MEDIA_LOCATION variables however I do specify internal paths for the upload/upload location and unsure if the upgrade will break things now, or is just something to adress in a future migration.

docker-compose.yml
services:
  immich:
    ...
    volumes:
      # Do not edit the next line. If you want to change the media storage location on your system, edit the value of UPLOAD_LOCATION in the .env file
      - ${UPLOAD_LOCATION}:/usr/src/app/upload/upload
      - ${LIBRARY_LOCATION}:/usr/src/app/upload/library
      - ${USER1_LIBRARY_LOCATION}:/usr/src/app/upload/library/User1
      - ${THUMB_LOCATION}:/usr/src/app/upload/thumbs
      - ${ENCODED_VIDEO_LOCATION}:/usr/src/app/upload/encoded-video
      - ${PROFILE_LOCATION}:/usr/src/app/upload/profile
      - ${BACKUP_LOCATION}:/usr/src/app/upload/backups
      - ${PHOTOPRISM_LOCATION}:/home/user/photoprism:ro ## External Library
      - /etc/localtime:/etc/localtime:ro


.env
# The location where your uploaded files are stored
#UPLOAD_LOCATION=/volume1/Master Backup/immich
UPLOAD_LOCATION=/volume1/Master Backup/immich/content/upload
LIBRARY_LOCATION=/volume1/Master Backup/immich/content/library
USER1_LIBRARY_LOCATION=/volume1/homes/<user_1>/immich/User1
PROFILE_LOCATION=/volume1/Master Backup/immich/profile
THUMB_LOCATION=/volume1/docker/Photo Managment/immich/thumbs
ENCODED_VIDEO_LOCATION=/volume1/docker/Photo Managment/immich/encoded-video
BACKUP_LOCATION=/volume1/docker/Photo Managment/immich/backups
PHOTOPRISM_LOCATION=/volume1/Master Backup/photoprism
# The location where your database files are stored
DB_DATA_LOCATION=./postgres
Was this page helpful?