mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 19:01:54 +00:00
kevinveenbirkenbachandClaude Opus 5.5
0f7fb92e12
Memcached, Joomla, Moodle, Odoo, Shopware, Snipe-IT and SuiteCRM set
their cache size, PHP memory_limit, OPcache, worker limits and search
heap as literals next to a mem_limit they never read. They now ask
lookup('service_memory_mb') for a share of that limit. The shares are
chosen so every rendered value stays what it was.
Where the parameter lives in a file that cannot hold a template, the
value is handed in: Shopware's init script reads INIT_PHP_MEMORY_LIMIT
and refuses to start without it, SuiteCRM's image takes it as a build
argument. Shopware's worker gets --memory-limit as a command appended
to its entrypoint, and Moodle's OPcache size moves from the static ini
into the rendered one.
The performance.php.memory_limit keys of Joomla and Moodle are gone
from services.yml; nothing else read them.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
8 lines
375 B
Django/Jinja
8 lines
375 B
Django/Jinja
memory_limit={{ MOODLE_PHP_MEMORY_LIMIT }}
|
|
opcache.memory_consumption={{ lookup('service_memory_mb', application_id, 'moodle', 0.125) }}
|
|
upload_max_filesize={{ MOODLE_PHP_UPLOAD_MAX_FILESIZE }}
|
|
post_max_size={{ MOODLE_PHP_POST_MAX_SIZE }}
|
|
max_execution_time={{ MOODLE_PHP_MAX_EXECUTION_TIME }}
|
|
max_input_vars={{ MOODLE_PHP_MAX_INPUT_VARS }}
|
|
date.timezone={{ HOST_TIMEZONE }}
|