Thanks for reaching out, and sorry for the late reply. I missed your original message.
No, it wasn’t possible before—now it is. Now you can use --fpm-admin-value to force the admin value to be written, or --fpm-value to force the user-level value to be written. If not set, it will default to existing logic, meaning it will preserve whichever value type exists.
You can use the following patch to make it work now:
For all domains, use the --all-domains flag. Use --fpm-admin-value to enforce the admin flag, --fpm-value to enforce the user flag; or set none to change whatever currently exists on the config or add a user value by default.
That does not answer what I am looking for - where does the --fpm-admin-value go (or what does it replace) in my example? I am not sure of the parameters surrounding --fpm-admin-value to make it work.
First of all, you’re missing on --ini-name param in your example.
--fpm-admin-value and --fpm-value are not values, those are the flags. It’s clearly described in the patch:
When updating PHP-FPM configuration, the --fpm-admin-value flag can be used to force a setting to be written as an admin-level directive (i.e. php_admin_value), and the --fpm-value flag can be used to force a regular user-level directive (i.e. php_value). If neither flag is given, the existing directive type is preserved where possible.
If this isn’t correct, I’d ask you give a full example of a valid command. I’m missing a basic concept somewhere, and without the surrounding context of what the flag is flagging, I don’t know what it is.
It will only update php_value[post_max_size] even if php_admin_value[post_max_size] also exists. If post_max_size doesn’t exist at all it will still add php_value[post_max_size]. If php_value[post_max_size] doesn’t exist but php_admin_value[post_max_size] does, then it will still only set php_value[post_max_size] and not php_admin_value[post_max_size].
These new flags let you enforce the type, that’s all.