php.ini directives

Adrien

Hello,

Would be nice if we could all share our php.ini directives. What it does and why you set it.
@AdamM spoke about php.ini in feature request.

It is good to set max_input_vars = 3000 for WordPress sites.

The PHP Max Input Vars is the maximum number of variables the server can use for a single function. To work properly with a modern WordPress theme set this value to 3000. If the value is too low, you may experience problems such as lost data within your Theme Options and disappearing widgets.

Screenshot enclosed of my max_input_vars = 3000 directive using enhance,
https://pasteboard.co/hJkjmF7XrJCj.png

Correct me if i'm wrong please @Adam @Aliysa_Enhance

necrom

Pretty basic at the moment:

mail.add_x_header = On
memory_limit = 1000M
post_max_size = 1000M
upload_max_filesize = 1000M

max_input_vars hasn't come up as a problem for us yet, but I will add it. It seems a pretty lame anti-DoS feature generally / should imho be set high by default for people to reduce if they want such increased resource protection.

nqnoc

necrom
What is the reason for using: mail.add_x_header = On ?

deydod

necrom
Your memory_limit seems dangerously high. I would consider max 512MB. Depending on your available ram and number of processes it can clog your server easily.
As for mail.add_x_header its good for debugging purposes, since it expose the filename of the script that is sending mail. Should be off on production servers.

necrom

nqnoc Sorry was away, it was to add the header to outbound email that would show the PHP path the email was sent from, but I've not checked if this is still working since email changes in v11.

necrom

deydod Our nodes run with hundreds of GB memory and the cgroup account limits prevent this becoming over stretched, the mail headers are necessary on the presently non-PCI capable shared IP servers to track down spam/exploit sources but will be selectively disabled when firewall management comes in future versions and we offer PCI-capable accounts.