immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-02-24 19:08:04 +03:00
Code Issues 783 Packages Projects Releases 12 Wiki Activity

Unclear onboarding message for "storage template engine" #2168

New Issue
Closed
opened 2026-02-05 05:25:41 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-05 05:25:41 +03:00
Owner
Copy Link

Originally created by @Cretezy on GitHub (Feb 15, 2024).

The bug

This message is unclear in the onboarding. What happens if the storage template engine is off? Does it use the default settings? This should be explained here

image

The OS that Immich Server is running on

Docker, Unraid

Version of Immich Server

v1.94.1

Version of Immich Mobile App

v1.94.1

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

N/A

Your .env content

N/A

Reproduction steps

Go through onboarding setup.

Additional information

No response

Originally created by @Cretezy on GitHub (Feb 15, 2024). ### The bug This message is unclear in the onboarding. What happens if the storage template engine is off? Does it use the default settings? This should be explained here ![image](https://github.com/immich-app/immich/assets/2672503/0abd2e88-dd5d-4c69-9503-5f8f8d4ef317) ### The OS that Immich Server is running on Docker, Unraid ### Version of Immich Server v1.94.1 ### Version of Immich Mobile App v1.94.1 ### Platform with the issue - [ ] Server - [X] Web - [ ] Mobile ### Your docker-compose.yml content ```YAML N/A ``` ### Your .env content ```Shell N/A ``` ### Reproduction steps ```bash Go through onboarding setup. ``` ### Additional information _No response_
OVERLORD added the good first issue label 2026-02-05 05:25:41 +03:00
OVERLORD commented 2026-02-05 05:25:57 +03:00
Author
Owner
Copy Link

@mertalev commented on GitHub (Feb 15, 2024):

You're right that we should explain what happens when it's disabled. It means that when assets are uploaded to the upload folder, they stay there instead of being moved based on the storage template.

The reason you might prefer this is if the move would be slow. In most cases, the move is done instantly by "renaming" the file to be in a different path. But depending on the file system, whether those two folders are in the same drive, whether they're network storage, etc., the whole file may need to be copied. This can cause a lot of disk wear, hence why it's opt-in.

@mertalev commented on GitHub (Feb 15, 2024): You're right that we should explain what happens when it's disabled. It means that when assets are uploaded to the `upload` folder, they stay there instead of being moved based on the storage template. The reason you might prefer this is if the move would be slow. In most cases, the move is done instantly by "renaming" the file to be in a different path. But depending on the file system, whether those two folders are in the same drive, whether they're network storage, etc., the whole file may need to be copied. This can cause a lot of disk wear, hence why it's opt-in.
OVERLORD commented 2026-02-05 05:26:02 +03:00
Author
Owner
Copy Link

@aviv926 commented on GitHub (Feb 19, 2024):

You're right that we should explain what happens when it's disabled. It means that when assets are uploaded to the upload folder, they stay there instead of being moved based on the storage template.

The reason you might prefer this is if the move would be slow. In most cases, the move is done instantly by "renaming" the file to be in a different path. But depending on the file system, whether those two folders are in the same drive, whether they're network storage, etc., the whole file may need to be copied. This can cause a lot of disk wear, hence why it's opt-in.

There is an explanation I previously added to the documentation, we can use it or put a link to it.
https://immich.app/docs/administration/backup-and-restore#asset-types-and-storage-locations

@aviv926 commented on GitHub (Feb 19, 2024): > You're right that we should explain what happens when it's disabled. It means that when assets are uploaded to the `upload` folder, they stay there instead of being moved based on the storage template. > > The reason you might prefer this is if the move would be slow. In most cases, the move is done instantly by "renaming" the file to be in a different path. But depending on the file system, whether those two folders are in the same drive, whether they're network storage, etc., the whole file may need to be copied. This can cause a lot of disk wear, hence why it's opt-in. There is an explanation I previously added to the documentation, we can use it or put a link to it. https://immich.app/docs/administration/backup-and-restore#asset-types-and-storage-locations
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:skip
changelog:translation
cli
date-time
dependencies
documentation
external-library
format
good first issue
mobile-beta
mobile-beta
mobile-beta
needs-answer
nice to have
pull-request
Mirrored from GitHub Pull Request
 sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label good first issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#2168
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?