docker-compose -> docker compose

Signed-off-by: simonhammes <simonhammes@users.noreply.github.com>

Author: simonhammes

README.APCng.md

@@ -47,7 +47,7 @@ The following table compares `APC` and `APCng` processing time for a series of o
 | APCng 100k keys / 2500 metrics |       274.7 |           84.0 |             34.6 |       4092.4 |                    52.9x |
 | APCng 1M keys   / 2500 metrics |       187.8 |           87.7 |             40.7 |       5396.4 |                    50.1x |
 
-The suite of engine-performance tests can be automatically executed by running `docker-compose run phpunit vendor/bin/phpunit tests/Test --group Performance`. This set of tests in not part of the default unit tests which get run, since they take quite a while to complete. Any significant change to the APC or APCng code should be followed by a performance-test run to quantify the before/after impact of the change. Currently this is triggered manually, but it could be automated as part of a Github workflow.
+The suite of engine-performance tests can be automatically executed by running `docker compose run phpunit vendor/bin/phpunit tests/Test --group Performance`. This set of tests in not part of the default unit tests which get run, since they take quite a while to complete. Any significant change to the APC or APCng code should be followed by a performance-test run to quantify the before/after impact of the change. Currently this is triggered manually, but it could be automated as part of a Github workflow.
 
 ## Known limitations
 One thing to note, the current implementation of the `Summary` observer should be avoided on busy servers. This is true for both the `APC` and `APCng` storage engines. The reason is simple: each observation (call to increment, set, etc) results in a new item being written to APCu. The default TTL for these items is 600 seconds.  On a busy server that might be getting 1000 requests/second, that results in 600,000 APC cache items continually churning in and out of existence.  This can put some interesting pressure on APCu, which could lead to rapid fragmentation of APCu memory. Definitely test before deploying in production.

README.md

@@ -143,7 +143,7 @@ composer require promphp/prometheus_push_gateway_php
 
 Start a Redis instance:
 ```
-docker-compose up redis
+docker compose up redis
 ```
 
 Run the tests:
@@ -157,16 +157,16 @@ composer install
 
 ## Black box testing
 
-Just start the nginx, fpm & Redis setup with docker-compose:
+Just start the nginx, fpm & Redis setup with Docker Compose:
 ```
-docker-compose up
+docker compose up
 ```
 Pick the adapter you want to test.
 
 ```
-docker-compose run phpunit env ADAPTER=apc vendor/bin/phpunit tests/Test/
-docker-compose run phpunit env ADAPTER=apcng vendor/bin/phpunit tests/Test/
-docker-compose run phpunit env ADAPTER=redis vendor/bin/phpunit tests/Test/
+docker compose run phpunit env ADAPTER=apc vendor/bin/phpunit tests/Test/
+docker compose run phpunit env ADAPTER=apcng vendor/bin/phpunit tests/Test/
+docker compose run phpunit env ADAPTER=redis vendor/bin/phpunit tests/Test/
 ```
 
 ## Performance testing
@@ -178,6 +178,6 @@ phpunit vendor/bin/phpunit tests/Test/ --group Performance
 
 The test can also be run inside a container.
 ```
-docker-compose up
-docker-compose run phpunit vendor/bin/phpunit tests/Test/ --group Performance
+docker compose up
+docker compose run phpunit vendor/bin/phpunit tests/Test/ --group Performance
 ```