Yup

Something weird is happening. When using ``` cache: redis: host: '{env.REDIS_HOST}' port: '{env.REDIS_PORT}' ``` running it locally (in and out container) - it works. When its deployed to production Kubernetes...

Couldn't be that avoided with https://getcomposer.org/doc/04-schema.md#provide ? Basically something like: ```json { "require": { "ext-intl": "*" } } ``` And giggsey/locale: ```json { "provides": { "ext-intl": "*" } } ```...

Tried to fix it, but failed miserably - but at least I added test case. :sweat_smile:

Same here.  Now i'm searching which products is undefined exactly.

There is https://keda.sh/docs/2.4/scalers/selenium-grid-scaler/ which can autoscale nodes, it's working fine - the problem is with tearing down a node. Since it doesn't keep track of which node is working -...

I would suggest decoupling the actual upload and url generation and even filename generation.

> If we are doing this for AWS, should we also do it for cloudinary or other providers? That's why I suggest to decouple url and filename generation and the...

I suppose it would be complex because Doctrine deprecated [PARTIAL](https://github.com/doctrine/orm/issues/8471) objects - so the recommended way now is to use `NEW` [syntax](https://www.doctrine-project.org/projects/doctrine-orm/en/2.9/reference/dql-doctrine-query-language.html#new-operator-syntax) - but that would mean that Api Platform...

+1 for exposing number of free/busy workers. It would allow to scale in advance, if there is some I/O blocking in workers, and they all become busy.

+1