tailscale-dev / tailscale-dev/ScaleTail
🐞 Bug: Immich - Changing UPLOAD_LOCATION in .env has no effect on where files are stored
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 124
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 4
Description
Bug Description:
I have a NAS with 2 storage pools and wanted to store my Immich library on the second pool. I changed UPLOAD_LOCATION in the .env file to point to a path on that pool, but Immich kept writing to the default ./immich-data/upload directory instead. The env var seems to be ignored.
Expected Behavior:
Setting UPLOAD_LOCATION in .env should control where uploads are stored.
Actual Behavior:
No matter what I set UPLOAD_LOCATION to, data always ends up in ./immich-data/upload.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the Docker Compose configuration and how it loads the .env file and references UPLOAD_LOCATION. Reproduce the issue with a path on a different storage pool, then verify that the generated volume mapping and Immich's upload location use the configured path instead of ./immich-data/upload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100