Add TYPO3 GFX configuration for ImageMagick6

[DanielSiepmann]

In order to configure system to process images. Otherwise possible
existing project configuration within LocalConfiguration.php might
prevent processing, due to configured GraphicsMagick or different paths.

Resolves: #1710

Automated Testing Overview:

I've didn't find instructions how to execute existing tests, therefore none were executed or adjusted or added.

Related Issue Link(s):

#1710

[CLAassistant]

All committers have signed the CLA.

[rfay]

This looks fine to me. My only question is what prompted the PR in the first place. I assume it was a result of the install happening on another host configuration, and the LocalConfiguration.php being checked in (which seems unusual), and thus the LocalConfiguration.php didn't have this properly in it?

[DanielSiepmann]

Yes, the use case we encounter are agencies migrating existing project to ddev. Therefore an LocalConfiguration.php already exists on production system, or within VCS already. Whether it's versioned depends on the agencies and people involved. We, as most of our customers, always track this file.

[rfay]

So although we'd expect LocalConfiguration.php to have "local configuration", it actually is general config, and stuff like credentials is always put into AdditionalConfiguration? I assume they're not checking credentials into LocalConfiguration?

Anyway, thanks for helping me understand.

[DanielSiepmann]

That depends on the users ;) Sometimes the AdditionalConfiguration is used to make use of a different loader, e.g. env or yaml loader.

But in context of ddev, this is the place where ddev can configure TYPO3 to work. We could also add something to the docs instead.

[rfay]

I wonder if there are other things that need to be overwritten by the AdditionalConfiguration for clients in this situation.

Anyway, I'm fine with this, I just have to manually test it.