-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing ini memory_limit and output_buffering #256
Comments
+1 The output buffer warning in Drupal status report has been coming up a lot for users of farmOS (a Drupal distribution that offers a Docker image based on this image). For production environments, the PHP base image recommends enabling default PHP production configuration in downstream images, which also enabled output buffering:
I don't think we can do that in this image, and it should be left up to downstream image maintainers/projects to implement. But it may be worth considering enabling output buffering in this image as a baseline, since without it Drupal's status report shows a warning. |
Yeah, enabling output buffering is 100% solid -- an explicit upstream recommendation is the best thing to convince me 😄 The memory limit is a little hazier -- they clearly recommend something, but the specific value they recommend is not as explicitly spelled out. 😞 |
Agreed. Also I think PHP's default |
as described at: drupal memory requirements we need at least 128 MB.
also as of 10.2.0, It is now recommended to enable output buffering in php.ini
The text was updated successfully, but these errors were encountered: