Proposed rewrite of PR #1161: apache_raise_php_limits [revised to apache_high_php_limits] for WordPress & Moodle #1165
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The httpd playbook now has the option of setting high limits in /etc/php/7.x/apache2/php.ini (for WordPress & Moodle) if you set
apache_raise_php_limits[since renamed to apache_high_php_limits] in /etc/iiab/local_vars.ymlThis was formerly done in the wordpress playbook.
This PR also:
allow_apache_sudotoapache_allow_sudoin roles/httpd/defaults/main.yml and elsewhere (as before, this is for easy poweroff in low-electricity environments etc, in the newly created roles/httpd/defaults/main.yml)Builds on #1147 PR #1161 [since modified by PR #1166]