NotionCommotion Posted December 17, 2014 Share Posted December 17, 2014 Per line 79 of the latest php.ini file (http://git.php.net/?p=php-src.git;a=blob;f=php.ini-production;hb=HEAD), the production php.ini file is recommended for both production and development. Agree? I would like to know the “typical” recommended changes to this file for both production and development. My requirements should be assumed typical with the following qualifications: Installed using yum on Centos Apache/2.2.15 MySQL (PDO) Either a physical machine or VPS (not a shared host) Primary US market Hopefully, this provides enough description, and if you still feel it totally depends on each individual’s unique needs, please let that remain unsaid. Below is my initial assessment: Line 445: Change error_reporting to E_ALL for development only. Line 462: Change display_error to On for development only. Line 473: Change display_startup_error to On for development only. Line 568: Leave error_log blank so they go to the SAPI Error Logger (what does this mean?) Line 656: Change post_max_size if specifically needed for the application. Ideally, this would be changes in a particular script, however, I don’t think this is possible. Line 676: Should default_charset remain at “UTF-8”? Line 799: Change upload_max_filesize if specifically needed for the application. Ideally, this would be changes in a particular script, however, I don’t think this is possible. Any other recommended changes? Thank you Quote Link to comment Share on other sites More sharing options...
Jacques1 Posted December 17, 2014 Share Posted December 17, 2014 The php.ini is big, and even the basic settings would require an entire tutorial. Sure, we could randomly pick a few directives, but that's rather useless. To fix obvious mistakes,use an ini scanner. If you want an in-depth discussion, pick a particular aspect like error handling, file uploads or whatever. Quote Link to comment Share on other sites More sharing options...
NotionCommotion Posted December 17, 2014 Author Share Posted December 17, 2014 Yea, it is BIG! I just went over the whole thing (however glossed over areas which I didn't think were as pertinent). Forgot if was the php.ini or the httpd.conf file that said "read and memorize every single line!" Well, maybe it wasn't that strong. Thanks for the ini scanner link. I will check it out. I agree that discussing the entire file is not realistic. I was looking for a starting point of areas I would want to better analyze and consider changing. The seven items appear to be ones I would consider doing. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.