Re: Using the installshield vs manually

It is not secure because it creates a php.ini file with default settings. It is better to choose your own settings in php.ini to suit your website and the enviroment it opperates it. It also uses default settings in your server configuration, which sometimes is not the best way to do it. If you only use the server for beta testing/development, install shield is fine on its own. Otherwise, it is best to customise the php.ini and check the server settings (Which is almosts as time consuming as just installing manually!). Stephen ----- Original Message ----- From: "Daniel Crompton" <dannycrompton@btopenworld.com> To: <php-windows@lists.php.net> Sent: Sunday, June 15, 2003 7:08 PM Subject: [PHP-WIN] Using the installshield vs manually Hi There are two ways to install php on win2k, either manually or using the installshield. I have always installed php using the windows installshield which has always worked perfectly. (win2k/iis) The paragraph below suggests you should not install php this way. Can anyone tell me why this says it is not secure?. Is there reason for concern re. my previous installations? TIA http://www.php.net/manual/en/install.windows.php#install.windows.manual Be aware, that this setup of PHP is not secure. If you would like to have a secure PHP setup, you'd better go on the manual way, and set every option carefully. This automatically working setup gives you an instantly working PHP installation, but it is not meant to be used on online servers.