Apart from composer scripts, I don't think these changes improve anything.

I don't want to improve performance or anything else. I just want to update the docker configuration to be more effective and make developing easier.

If you look at the current dockerfile, in the last line, it is installing dependencies and run the tests. which means to run the tests, I have to build the dockerfile each time?
It's obvious developers must build dockerfile the first time and then run the tests using command line inside of the countainer.

Another update for the project's structure can be using StyleCI instead of PHP Code Sniffer. StyleCI can be configured to fix the code style using an automated merge commit.
Fixing code style after every change (after the pipeline failed mostly😅) is annoying.

If you look at the current dockerfile, in the last line, it is installing dependencies and run the tests. which means to run the tests, I have to build the dockerfile each time? It's obvious developers must build dockerfile the first time and then run the tests using command line inside of the countainer.

The last line is the default command when you run the container.

docker-compose run --rm tests

Note that I don't use this docker image to develop because the integration with PHPStorm and xdebug set-by-step debugging is hard to setup.

So I just found that the memory limit is too low. This lines should be added after docker-php-ext-install -j$(nproc) zip.

 cp /usr/local/etc/php/php.ini-development /usr/local/etc/php/php.ini && \
 echo "memory_limit=-1" >> /usr/local/etc/php/php.ini

Another update for the project's structure can be using StyleCI instead of PHP Code Sniffer. StyleCI can be configured to fix the code style using an automated merge commit.
Fixing code style after every change (after the pipeline failed mostly😅) is annoying.

Not all CS issues can be fixed automatically, but in 90% of cases, we could make it easier for external contributors to contribute by automatically committing modifications proposed by phpcbf.

The last line is the default command when you run the container.

It had never run tests on my computer. It is even mentioned here.

we could make it easier for external contributors to contribute by automatically committing modifications proposed by phpcbf.

So you mean it can be done automatically? How?

we could make it easier for external contributors to contribute by automatically committing modifications proposed by phpcbf.

So you mean it can be done automatically? How?

As proposed by @Treggats in #2664.

As proposed by @Treggats in #2664.

That's interesting, I might work on that PR next. Seems an important PR and the best opportunity for me to work with PHPStan.

As proposed by @Treggats in #2664.

Thanks for the reminder that I needed to check the test suite. Hope that I can open it pretty soon

Edit
I've opened #2664 for review again.

I don't have any more changes to propose and I think it's the end of this PR.
Please take every feature that you find helpful and revert the rest.

If you want to merge this PR, you can do it after merging #2664. I think there are some conflicts.

Conflicts resolved.

I updated the branch with the followings:

• Revert the PHP_VERSION argument, so it's easy to test with other PHP versions. Even if that's not the main usage, but it would necessary to debug errors specific to a PHP version.
• Set the ini config in phpunit.xml.dist, it's possible to change them by creating the phpunit.xml
• Composer scripts automatically resolves binaries in vendor/bin
• Add a default command for docker-compose run app, that install vendors and run tests. docker-compose run app bash is recommanded if you need to tests many times without restarting the container.

Thank you @hans-thomas