![]() /usr/local/directadmin/data/users/username/php/php-fpm72.custom1./usr/local/directadmin/data/users/username/php/php-fpm56.custom2./usr/local/directadmin/data/users/username/php/php-fpm56.custom1.When checked, the CUSTOM1/CUSTOM2 tokens will be saved to the php-fpm customX files, for all active php versions (as set in the nf). There is also the "save to all php versions" which copies your data to all custom tokens for each php version. ![]() The bottom 2 boxes, as before, will only apply to that given php version. When you save data into either of these fields, the CUSTOM1/CUSTOM2 tokens set to span all php versions that the User may select from. But both global and per-php, if present, will end up into the same token. Which will be set into the CUSTOM1/CUSTOM2 tokens before the 1 files (for example). /usr/local/directadmin/data/users/username/php/2./usr/local/directadmin/data/users/username/php/1.You may edit configuration manually by modifying files: 2 new textareas in the Custom Httpd Config -> : php-fpmXX page for "global php-fpm CUSTOM1" and "global php-fpm CUSTOM2" With the more common use of the php version selector, you may want your custom php-fpm configs to span all php versions. If either exists, they'll be added into their respective CUSTOM1 or CUSTOM2 tokens for all nf rewrites. /usr/local/directadmin/data/templates/custom/2./usr/local/directadmin/data/templates/custom/1.To create true global CUSTOM1 and CUSTOM2 pre tokens, loaded in before other tokens for the nf templates, all Users, all php versions, create the following files: # I wish to have global custom PHP-FPM configuration This should override the default value from the template.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |