|
Friday 06 February 2009 7:08:44 am
I am not a su-php expert, but the doc says that it can be configured to use a php.ini file from a given directive, via the suPHP_ConfigPath directive.
This means you can put your php.ini eg. at the eZ Publish root and have it always used by any php script run by your webserver, be it index.php or within aany subdirectory (I imagine you will have a vhost section in the Apache file that is under the control of the hosting providers but that is dedicated to your website, where suPHP_ConfigPath is set). I would not recommend running eZ Publish without an (Apache) rewrite rule that redirects all accesses through the index.php file, unless really necessary. About running php scripts designed to be run from the command line: first of all they will not activate at all if run via the webserver, and that is a security measure. They are designed to be run by the site admin, not by any site visitor going eg. to http://mysite/bin/php/ezsubtreeremove.php. This also applies to runcronjobs.php, and since you are quite likely to need at least a couple of the eZ cronjobs running, you should see if you can have cronjobs set up in your environment. Second is, if you have a shell access to invoke those scripts using php in cli mode, you can invoke php using the -c option, or setting up the PHPRC env var. Both options tell the php interpreter where to find the ini file, so you do not have to symlink it all over the place. It is quite common to have eg. one php.ini for the webserver and a different one for cli scripts.
Principal Consultant International Business
Member of the Community Project Board
|
