Can't add custom configurations to pools

[diegosolo]

Hi! I've been trying to make my server parse html files as php files with no success. The problem is that I need to set the line security.limit_extensions = .php .html in the pool configuration of each site (it doesn't work if I place it under [www] in www.conf).

As it is, the web interface doesn't allow me to do this. I tried setting this line manually under my pool in php-fpm.conf (which worked, momentarily) but as soon as there are any changes to the configuration the files are rewritten and the configuration is lost.

Do you consider it possible/convenient to add a text field for custom configurations in the "Content" tab of the "Websites" section? Another option is to put a specific field "Limit extensions", which would be good as long as you don't need other configs to be added in the pool.

Note: i'm aware of security risks related to this matter. In case this update is accepted I'd recommend a warning next to the field.

[diegosolo]

I've added a field in my install to set the value for limit_extensions. I could make a PR with this if the comunity thinks it has value.

[rkkoszewski]

I have a similar issue. In my case it's the PHP Environment variables. It would be awesome if there would be an option to enable the environment variables or just allow to paste raw configuration data to the php-fpm.conf file (Like the advanced options in Nginx).

I would need to add this:

env[HOSTNAME] = $HOSTNAME
env[PATH] = /usr/local/bin:/usr/bin:/bin
env[TMP] = /tmp
env[TMPDIR] = /tmp
env[TEMP] = /tmp

@diegosolo Where did you find the file in Ajanti that generates the php-fpm file? Maybe I could just hardcode the pool configuration in Ajanti (At least temporarily).

[diegosolo]

Hi @rkkoszewski! I added one field to the PHP7.0-fcgi form, editing two files (just copying another field and changing it): the front-end and the back-end.

Anyway, the project doesn't seem to be actively maintained anymore, reason why I moved to Sentora.