chassis / imagick

A Chassis extension for Imagick/ImageMagick

Imagick/ImageMagick

A Chassis extension to install and configure ImageMagick on your server.

Usage

1. Add this extension to your extensions directory. git clone [email protected]:Chassis/imagick.git extensions/imagick
2. Run vagrant provision
3. ImageMagick has been installed on your Chassis VM!

That's it!

imagick's Issues

Add support for Extensions V2

http://docs.chassis.io/en/latest/extend/#extensions-api-v2

Add support for `disabled_extensions`

We should add the ability to remove Imagick

Add issue template

Remove .github as we have a global one for the organisation

Command-line imagick tools

Hi, using this extension and I can see it's in place; same settings as my live env, which is a win :)

$ php --info | grep imagick
/etc/php/7.0/cli/conf.d/20-imagick.ini,
imagick
imagick module => enabled
imagick module version => 3.4.3
imagick classes => Imagick, ImagickDraw, ImagickPixel, ImagickPixelIterator, ImagickKernel
imagick.locale_fix => 0 => 0
imagick.progress_monitor => 0 => 0
imagick.skip_version_check => 1 => 1

However, I can't access any of the cli tools, for example:

$ identify
-bash: identify: command not found

In production, this would spout all the usage notes.

Is there something else needed in this extension to be able to use command-line Image Magick tools?

Support WebP

I was having a read through this post: https://make.wordpress.org/hosting/2022/03/30/wordpress-hosting-and-webp-support/ and it looks like we should ensure that WebP is supported.

apt-get install libwebp-dev should install the package we need so we should just be able to add that package into this extension.

Account for PHP versions correctly

Currently if you set php: 8.0 and run vagrant provision you'll end up in a situation where the PHP cli ends up on 8.1 but fpm is on 8.0 this isn't ideal so we should fix it!

Provisioning fails with a default Chassis installation

A new Chassis installation with a yaml file like so:

extensions:
  - imagick

will cause the following issue:

Props @peterwilsoncc for reporting this!