How is the storage template engine supposed to work?
Hello everyone! Apologies if this has been discussed elsewhere—I couldn’t find a definitive answer on GitHub, in the issues, or on Discord. I’ve read the storage-template docs (https://immich.app/docs/administration/storage-template) and everything else I could find online, but I’m still puzzled by how this feature works in practice. I’ve set up Immich several times, and I’m not sure whether this is intended behavior, an issue with my setup, or simply my own unrealistic expectations. Please enlighten me!
My docker-compose.yml: https://cloud.taking.pictures/s/qGG8cxSKgZQsAHS
From the docs and the UI, I expected the storage template to:
* Replicate any album structure I create in Immich (via web or mobile) into my filesystem, according to my template settings
* Automatically apply changes to the filesystem whenever I move a file between albums or add a file to an album
* Essentially run the “migrate storage template” job on every asset change, so that my filesystem always (near real-time) mirrors my album structure
What I actually see is that no replication occurs unless I manually trigger the migration job in the web UI. In the logs, I only see this output when I run it manually—I had hoped it would run automatically whenever I move an asset or edit an album:
Is this the intended behavior? If automatic triggering isn’t supported, could I instead use the Immich CLI in a cron job to run migrations at regular intervals, so that my filesystem stays in sync at all times?
I would greatly appreciate your insights on this matter.
Thank you in advance!
My docker-compose.yml: https://cloud.taking.pictures/s/qGG8cxSKgZQsAHS
From the docs and the UI, I expected the storage template to:
* Replicate any album structure I create in Immich (via web or mobile) into my filesystem, according to my template settings
* Automatically apply changes to the filesystem whenever I move a file between albums or add a file to an album
* Essentially run the “migrate storage template” job on every asset change, so that my filesystem always (near real-time) mirrors my album structure
What I actually see is that no replication occurs unless I manually trigger the migration job in the web UI. In the logs, I only see this output when I run it manually—I had hoped it would run automatically whenever I move an asset or edit an album:
Is this the intended behavior? If automatic triggering isn’t supported, could I instead use the Immich CLI in a cron job to run migrations at regular intervals, so that my filesystem stays in sync at all times?
I would greatly appreciate your insights on this matter.
Thank you in advance!
