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
It would be really nice if there was a built-in way to preserve the input directory structure in the output directory.
We don't want to save the AVIFs to the same folder as the source images as the CMS media browser will show both, but for easy try_files configuration we'd like to mirror the directory structure in the destination. Plus it keeps the folders with a manageable number of images in them.
(Having an option to append .avif would also be cool, to mirror how our bash script has been doing it. So the output file name is baz.jpg.avif. That way the try_files usage stays simple.
The text was updated successfully, but these errors were encountered:
Hi Peter, these are great ideas, very happy to accept a PR for either/both.
The use of input structure to determine output structure should probably be the default behaviour anyway, and therefore a semver major bump.
Making the use of try_files easier is a nice touch but should be opt-in, perhaps via something like an --append-extension or more explicit --try-files option or similar.
Thanks for writing this script!
When using
It would be really nice if there was a built-in way to preserve the input directory structure in the output directory.
We don't want to save the AVIFs to the same folder as the source images as the CMS media browser will show both, but for easy
try_files
configuration we'd like to mirror the directory structure in the destination. Plus it keeps the folders with a manageable number of images in them.Example:
(Having an option to append
.avif
would also be cool, to mirror how our bash script has been doing it. So the output file name isbaz.jpg.avif
. That way thetry_files
usage stays simple.The text was updated successfully, but these errors were encountered: