Jan Mikeš

Definitely QR for me.

Note that not every monorepo has exactly the same setup :-). Btw even in the article you are referencing to, there is exactly the same issue -> only one `/vendor`...

If there was a possibility, to set `\NunoMaduro\Larastan\ApplicationResolver::resolve()` a path to composer.json, it would solve the issue. It could be phpstan parameter, env variable, maybe something else 🤔

Sure, will do, 1st i wanted to discuss the possibilities. Btw it is kind of related to the `larastan/bootstrap.php` file -> given that there is no `bootstrap/app.php` in the root...

Sure, our monorepo structure is like this (trimmed it a little from utility dotfiles like .gitignore for example): ``` microservices/ microservices/microservice-a/ microservices/microservice-a/composer.json microservices/microservice-a/phpstan.neon microservices/microservice-a/src/ microservices/microservice-a/bootstrap/app.php packages/ packages/package-a/ packages/package-a/composer.json packages/package-a/phpstan.neon packages/package-a/src/...

Im not sure i fully understand here :-) > to change to every subdirectory and issue composer exec -- phpstan this is currently not possible as it causes the error...

My wish is `to change to every subdirectory and issue composer exec -- phpstan` But i believe that the library should support both ways and leave the decision on the...

Sorry for the delay. Works great now, thank you!

Hi, this is still relevant. For us, when the sentry is under higher load, it starts buffering requests to temp file and (i believe it is related, nginx starts responding...

Hi @vicpara the best way is to build your own image locally. You can get some inspiration here: https://github.com/JanMikes/celadna.cz/blob/main/strapi/Dockerfile