Re: virtual domain own php.ini
| From: | pan | Date: | Thu, 22 Apr 2004 19:38:52 +0000 |
| Subject: | Re: virtual domain own php.ini | ||
| References: | 1 2 3 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-184284@lists.php.net to get a copy of this message | ||
"John Nichel" <john@kegworks.com> wrote in message
news:40881D4E.1010607@kegworks.com...
> pan wrote:
> > "Robby Russell" <rrussell@commandprompt.com> wrote in message
> > news:4087D404.7000500@commandprompt.com...
> >
> >>Trying to use own php.ini file (rather than the one that the webserver
> >>sees by default) for a web site (on a box that has many websites that
> >>utilize the other) and used the following instructions, but it doesn't
> >>seem to notice my own php.ini file.
> >>
> >> > When the PHP interpreter starts up, it behaves according to settings
> >> > specified in any availabe php.ini file. The Web server will look for
> >> > this file in the following locations and in the following order:
> >> >
> >> > 1. The directory from which the PHP script was called 2. The root of
> >> > your Web directory 3. The Web server's default php.ini
> >>
> >>Any thoughts?
> >>
> >
> > rtfm on ini_set()
> >
>
> That's not going to help the OP load a seperate ini file for virtual
> domains. ini_set() is good if you only need to change a few settings,
> but it would be a pain to set all the ini settings (not to mention that
> I don't think ini_set() will change all the ini settings).
>
OP is on a virtual server
real world experience says ini_set is going to be what you can do
sorry for being cryptic and abrupt, but short answer seemed best