OSX php+apache+mysql setup wtfs
comments | Posted in osx | php on Tuesday, August 28 2007 12:45:00 PDT
So the OSX gui is nice and all, but on using the setup of php+apache provided to me that I found a few WTFs with regards to "the Mac Way" I've been exposed to:
- Why is the install of PHP we're using provided by an external package called Entropy. Why does entropy decide to break the Apache mold and configure its Apache directives within its own .conf file included at the end of httpd.conf. I've only ever seen approach on a Mac ... I guess Entropy is too good to just write in its directives inside httpd.conf
- why did the maintainer of Entropy decided to disable short_open_tags by default. I'm sorry but a developer is trying to configure something merely to function, and operate properly. Please don't make production mode settings for software upon install. The simplest valid php code block should work to test the LAMP stack:
<? phpinfo(); ?>I know that code is not production ready, or standard, but if I goto the page expecting to see PHP output and all appears broken. I have to hunt down the LAMP stack for the culprit: - .htaccess file
- included vhost entries appended to httpd.conf
- httpd.conf
- why did the maintainer of Entropy decided to disable short_open_tags by default. I'm sorry but a developer is trying to configure something merely to function, and operate properly. Please don't make production mode settings for software upon install. The simplest valid php code block should work to test the LAMP stack:
Since code delimiters can be any of the valid formats:
<?php ;?> or <? ;?> or <% ;%> or
don't force me to you yours by default. Thanks. I understand 1) standards 2) howto tune PHP+MySQL+Apache for any given project ... I'll get to the tuning later, not now when I'm just trying to configure everything to work.
thank god for apachectl configtest and eventually seeing the parsed +entropy-php.conf file listed (who names their files with symbols anyways?)
1. Apache said: Syntax OK
2. normally symboled filenames lead me to believe its a temporary, hidden file and unimportant.
of course LoadModule libexec/libphp4.so and its decendants are commented out. So that when anyone sits down at a new system on which Apache or PHP has never been run ... its a mess to figure where relevant files and directives are located. Whether the system is php4 ready or php5 ready.
MySQL OSX system preferences shows the username to startup the MySQL service is "David Gurba" and my root password. No its not, its really root and my password. This was only a little wtf and I quickly fixed the problem ... but why does the Admin panel allow for "David Gurba" and his password to start the service, but a typical MySQL connection string not allow that username. Just Odd and wtf.
So it all works (Yea!) but where is mysql.sock located?