Added PHP_CLI_MEMORY_LIMIT envvar to configure php cli memory limit

[nicksantamaria]

Motivation

After reducing the PHP_MEMORY_LIMIT envvar on content-vic, builds started breaking due to hitting memory limits in the cli container.

Changes

• Removes fpm worker limit from CLI container (this container doesnt run a fpm processs so its cruft that can be discarded)
• Adds a new envvar PHP_CLI_MEMORY_LIMIT that specifically targets the CLI container.
• PHP_CLI_MEMORY_LIMIT has a default value of 1024M
• Adds some missing docs for the metrics exporter.

Testing

Check out this branch and build image

docker build -t test -f Dockerfile.cli .

Run the image and check for the memory_limit value.

docker run --rm -it -e PHP_CLI_MEMORY_LIMIT=1024M test php -i | grep memory_limit
memory_limit => 1024M => 1024M
docker run --rm -it -e PHP_CLI_MEMORY_LIMIT=-1 test php -i | grep memory_limit
memory_limit => -1 => -1

[GROwen]

Did you mean to delete this?

[anthony-malkoun]

Why are these lines being removed?

[nicksantamaria]

Oh just noticed these to clean up - no fpm process in the cli container so we dont need the worker config here at all. Just cruft.

The same line still exists in the fpm image.