Q. How can we permanently increase PHP-FPM pm.max_children on self-hosted coolify?

[ckarsan]

Is there a way to pass environment variables (like PHP_FPM_PM_MAX_CHILDREN) to the core Coolify container that persists across updates?, as doing a check of logs on an unhealthy coolify container gave a warning about max children being reached.
Maybe a memory issue on my system which is 4GB ram, with around 7.5GB swap, and i was trying to deploy a Vite project using nixpacks
Maybe there could be some way to set in the UI ?