I don’t know since how long, but I just found out that there’s already a stable version of MySQL to run on OS X “Leopard”. You may find a download link at this URL.
I haven’t installed this new version yet, but as I red it fixes all the issues from the previous versions, particularly the one about having the MySQL extension in the preferences pane of the system. This new version is also supposed to run better and faster on Intel based Macs. Well, let’s see, I’ll update this post as soon as I have done some serious testing with it.
As I posted previously I’m now running MAMP as I wait for a nice PHP 5 package to be available. I did some research about how MAMP handles the htdocs folder, which is the one where you should have you web pages stored, and here are my findings. MAMP is designed to be self-contained, meaning it will not work if the htdocs folder is outside the MAMP folder in your applications, however, I just, accidentally, found a way of doing this and actually keep MAMP working.
If you open the httpd.conf file in /Applications/MAMP/conf/apache and scroll all the way down, you will find the virtual hosts section, in this section add a new virtual host, like this:
NameVirtualHost *
<VirtualHost *>
ServerName localhost
DocumentRoot “/Users/Stefan/Sites”
</VirtualHost>
In the previous example /Users/Stefan/Sites is where I have my pages stored and each time I call http://localhost in my browser MAMP will actually load the pages from there, so I have no need of moving everything into the MAMP’s htdocs folder.
You can add as much virtual hosts as you like and place them wherever you like, and MAMP will load and parse them just fine. You’re actually tricking it into believing the files are stored where they “should”.
Another one, it’s pretty nice to have PHP 5 bundled with Leopard, but it’s a very basic version of PHP, I guess the only library compiled into it is MySql, theres not even GD, so you will need to compile PHP on your own including all the libraries you need to get it to run. Honestly I’m to lazy for that right now so I just got MAMP up and running for now, until Marc has a compatible version to distribute.
I’ll keep you posted.
Amazing! I just completed the entire install, configuration, set-up and finally everything seems to be working on my Mac as it should, but nothing in life is perfect and here we go.
Take important notice of this!!!
When I installed Leopard I chose the default file system (HSFX) which means the HDD will be case sensitive, meaning you can have test.jpg and test.JPG in the same folder and the OS will handle them as different files, which is just what I need for my developing work. However Adobe does not support this format.
I went on to install the CS3 package and got an interesting notice:
After doing some research I found out that Adobe just does not support this file system in their installations since it’s apparently inconceivable that anyone would ever need case-sensitivity as the default file system, so they choose not to support it… I would say they could easily publish that case-sensitive file systems are not supported in the package system requirements or perhaps include anything in the FAQ or general support sections.
Getting CS3 to work would take a reformat and reinstall of my system drive since they use some of the built in frameworks and the system needs to know where to find them.
Never mind that thousands of third-party developers seem to be able to write applications that both leverage system frameworks and work without a hitch on my “unsupported” file system.
Be wise, take a look at this before upgrading to Leopard:
- Applications not compatible with Leopard
- (www.unsanity.com) Compatibility
I have spent my last hours on installing the all-new Leopard on my Mac, it actually went pretty fast. I haven’t had much time to check out the entire thing as I’ve been busy setting up my development environment (Apache, PHP, MySQL).
The good thing is that Leopard ships with Apache 2 and PHP 5.2 pre installed, so you only need to make a couple of changes to get Apache and PHP running in no time, I’ll explain how to do that. The bad news is that the current MySQL package file does not fully work on Leopard, well, the engine actually works, it’s the preference pane that does not work yet, so you won’t be able to use that to stop and start you MySQL DB, I’ll post a nice trick to get that running as well.
