No prompt and .platform.app.yaml ignored

[adriendupuis]

Hi,

Moving from ddev/ddev-platformsh to ddev/ddev-ibexa-cloud, I had to adapt too many things.

1. ddev get ddev/ddev-platformsh used to prompt for, at least, Platform.sh API token, project ID and environment name. With ddev-ibexa-cloud all this must be priorly set as DDEV web env configs or an error will occur when getting the add-on (for example “Please make sure you have set IBEXA_PROJECT”).
2. ddev-platformsh used to get the PHP version, some services (like Redis) to install, and run the hooks from .platform.app.yaml. ddev-ibexa-cloud doesn't. The PHP version must now be manually set as DDEV web env config or the default might not match the project one. composer install must be run manually. Redis isn't installed. etc.

You can possibly see all the changes I had to make in ibexa/documentation-developer#2599

Best regards,
Adrien

[nicogommen]

Hey @rfay , these are the questions from Ibexa that I was mentioning in our other issue 🙂

[rfay]

Hi @adriendupuis - ddev-ibexa-cloud is unrelated to ddev-platformsh

ddev-ibexa-cloud's job is to make ddev pull ibexa-cloud work, and that's about all. It's not aiming to do the things that ddev-platformsh tries to do.

• ddev-platformsh's job is to attempt to translate Platform configuration into DDEV configuration.
• ddev-ibexa-cloud's job is just to make ddev pull ibexa-cloud work (and probably ddev push ibexa-cloud, but that's discouraged for most usages.

I don't know if it's possible to use the two add-ons together. If ibexa-cloud usually has a .platform.app.yaml, you probably can.

Please take a look at the README again to see what the goal of this add-on is.

[adriendupuis]

Hi @rfay,

I manage to use both add-ons at the same time. It fixes PHP version, Redis, and self-installation. Because they don't share their env variables, I have to give the same information (too) many times.