| Re: Figure out path to php.ini [message #173510 is a reply to message #173498] |
Sat, 16 April 2011 16:41   |
Twayne
Messages: 135
Registered: September 2010
Karma:
|
Senior Member |
|
|
In news:4da8b7f7$0$6876$9b4e6d93(at)newsspool2(dot)arcor-online(dot)net,
Jo Schulze <antispam(at)feuersee(dot)de> typed:
> Twayne wrote:
>
>> In
>> news:4da80cac$0$6885$9b4e6d93(at)newsspool2(dot)arcor-online(dot)net,
>> Jo Schulze <antispam(at)feuersee(dot)de> typed:
>
>>> The predefined const PHP_CONFIG_FILE_PATH should contain
>>> the directory where php.ini is located.
>>
>> True, but to a newbie it could get confusing with all
>> the php.ini files strewn around his hard drive. They
>> aren't all the same, where a phpinfo on the server gets
>> you the exact information you need.
>
> I beg you pardon but if you have a bunch of php.ini files
> strewn around your hard drive, you have a probem. There
> should be one php.ini for every SAPI avali, which limits
> the number to a max of 3 (CLI, webserver module and
> websever CGI). Well, thinking of it, possibly several
> webservers are running at different ports, but for a
> productive environment I say that you'll have a limit of
> 2 (CLI and whatever for HTTP access).
There's one for local server, others for remote serving, a "bible" of
important parts, etc.. It's not unusual and occurs on many of them. I'm not
going back to see what each one is for, but it's all clearly documented. A
newbie however, discovering he needs to work on php.ini can pretty easily
get confused if he's the sort, as many are, who won't RTFM.
So, no, I do not have a problem; you do, in that you think you can paint
the whole world in one color. Don't not woik dat way.
>
>> Also,
>> if it's a turnkey freebie like there are so many of
>> these days, it wll be pretty well spelled out n the docs
>> that accompany it.
>
> Huh?
if it's a turnkey freebie like there are so many of
these days, it wll be pretty well spelled out n the docs
that accompany it.
Hard of reading/hearing?
>
>> BTW, I haven't seen any yet that provide the right
>> security settings for
>> either being a server to the outside world or just for
>> testiing, etc. etc.. They leave that up to the user
>> since there are so many different ways to do it. Keep in
>> mind I've only looked at the freebies that allow easy
>> setup for local server capability. Testing of code in
>> other words.
>
> There is pretty much documentation about how to secure PHP
> installations, if that was your question.
I don't recall the OP's original exact question any longer but that's one of
my points. RTFM. Additionally, those instructions are part of the download
package in most cases, not something you have to go googling for.
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]