This module provides a task, ConvertImagesToWebpTask
, which is to be
run periodically to provide WebP substitutes for all existing public
images.
- silverstripe/framework ^4.4
- Conflicts with silverstripe/s3 because this module works only with the default, filesystem-based asset manager.
composer require quinninteractive/silverstripe-webp-substitution ^2.0.0
See License
If you should need to change the assets-relative directory or the file suffix to be used for WebP images, you can do that in the configuration.
There is a default limit of 32 megapixels, over which conversion is not
attempted. This is to avoid overtaxing the server's virtual memory. This
setting can be overridden as shown below. If you change the
webp_file_suffix
, you must also change the suffix in your nginx
configuration (see example below).
QuinnInteractive\WebPSub\Task\ConvertImagesToWebpTask:
webp_directory_path: '.misc/.WebP'
webp_file_suffix: '.wp'
size_limit_megapixels: 16
sudo -Eu www ./vendor/bin/sake dev/tasks/webpconvert
DOCROOT=/var/silverstripe/live/current/docroot
SAKE=./vendor/bin/sake
SUDO=/usr/local/bin/sudo
# WebP graphics conversion task every hour
50 * * * * (cd $DOCROOT && $SUDO -Eu www $SAKE dev/tasks/webpconvert) > /dev/null 2>&1
To support this module, add these items to your existing Silverstripe configuration. If you have changed the YAML configuration, you will need to adjust these items accordingly.
# webp dir to try, if we accept webp (or none if not)
map $http_accept $webp_dir {
default "";
"~*image/webp" "/assets/.webp/";
}
map $arg_nowebp $accept_webp {
default $webp_dir;
'1' "/fail-on-purpose/";
}
# first try to return allowed webp
location ~ ^/assets/.*\.(?i:gif|jpeg|jpg|png)$ {
try_files $accept_webp$uri.webp $uri /index.php?$query_string;
}
# Never serve .protected, nor .webp not served above
location ~ ^/assets/\.(webp|protected)/ {
return 403;
}
TBD
If it can, the task will create the directories that it needs. If not,
you must create the .webp
directory (or the directory named in the
webp_directory_path
configuration) under the assets
directory and
make it writable by the web server.
2.1.1
Silverstripe 5 support.
This version introduces a backward-compatible feature so that converted WebP files are not used in the CMS. To take advantage of this new feature, you need to change your nginx configuration (see example above). If you do not make the changes, your site will work just as it did in earlier versions, so this is a non-breaking change.