You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, images (products, categories, etc.) are stored either in the database or on disk (according to "Media.Images.StoreInDB" setting).
If they are stored on disk, they are saved directly into the “images” directory. We have the application running in Docker, where we already have volumes set up for the directories “images/thumbs” and “images/uploaded”. Product images are currently stored in the SQL database.
We would like to store these images on the filesystem as well, but they will be stored directly in the “images” directory. We don’t want to create a volume for the entire “images” directory because it contains subdirectories like “flags”, which we don’t want to include in the volume.
As a possible solution, I thought of:
Saving images into the subdirectory, fe “images/pictures”.
Adding a setting in the configuration where the name of the subdirectory can be specified, e.g., "Media.Images.Subfolder", which by default would be empty (so backward compatible) but could be adjusted to the desired value.
The text was updated successfully, but these errors were encountered:
AndreiMaz
changed the title
Enhancement: Saving Pictures to a Directory on Disk to specific subdirectory
Saving pictures to a directory on disk to specific subdirectory
Oct 25, 2024
nopCommerce version: 4.70
Currently, images (products, categories, etc.) are stored either in the database or on disk (according to "Media.Images.StoreInDB" setting).
If they are stored on disk, they are saved directly into the “images” directory. We have the application running in Docker, where we already have volumes set up for the directories “images/thumbs” and “images/uploaded”. Product images are currently stored in the SQL database.
We would like to store these images on the filesystem as well, but they will be stored directly in the “images” directory. We don’t want to create a volume for the entire “images” directory because it contains subdirectories like “flags”, which we don’t want to include in the volume.
As a possible solution, I thought of:
The text was updated successfully, but these errors were encountered: