Goodbye Old Proprietary Friend...

I've been using MAMP Pro for some years now for my local Drupal development environment in Mac OS X. The prospect of MAMP is alluring, it promises point and click creation of website environments locally on your Mac with database, Apache and all. But the reality is that MAMP is a proprietary software wrapper which in the end turns out to be pretty buggy. This past year, the MAMP website was down for several days with not a peep out of them on Twitter so this was probably a sign to move on. With the latest upgrade for Mac OS X (10.8.2), my MAMP Pro installation broke and I was not able to fix it after hours of hair pulling. I checked in the MAMP forums and several users were having similar issues but there were no real answers to be had. I am sure I could have emailed for support but at this point, I was so done with MAMP.
Hurrah For Open Source, Long Live Open Source!
So I got fed up with all this malarkey and I figured that if I am developing using open source software with Drupal, it would be a good idea to make the effort to be all open source with my local server stack. It turns out this was not that much of a stretch and there is a great tutorial for Mac OS X 10.8 I followed the steps in that post and it worked well. Props to Apple for having Apache and PHP built in to Mountain Lion and pretty easy to get going. Activating PHP involves the 'ardious' task of uncommenting out one line of code but you will probably want to tweak your php.ini as well.
Customize it...
I created my own custom my.cnf file for better MySQL defaults, but I had to use a bit of Google-Foo to find some optimal settings. I placed the file in /etc and restarted MySQL and now my custom my.cnf settings were recognized. I also created a launch page in my "Sites" directory with all my local Drupal dev sites. If I go to localhost/~my_username/ in my browser, my custom launch page comes up. To achieve this, simply place an index.html page at the root of that directory, edit it by adding all your local dev links and you are good to go. In OS X, if you are not sure of your actual username, go to terminal and type whoami and you will then see your username.
Stable and Fast
So far, this new setup seems really stable and fast. I am using and getting more comfortable with Terminal to run some mysql and apache commands but I am used to this after finally getting dialed in to Drush and Git. The bottom line is, it feels more cool now when I am theming with Drupal knowing that I have left the ungainly mess of proprietary behind.
Comments
James (not verified)
Fri, 11/09/2012 - 19:05
Permalink
Better Option
A better choice is to free yourself of the proprietary Mac ecosystem all together and run a Linux distro. That is if you are truly serious about open source / software freedom.
Danny Englander
Sat, 11/10/2012 - 14:29
Permalink
I anticipated someone saying
I anticipated someone saying that but that's where I draw the line, I love OS X's UI / Ux and would not go that far. I use the right tools for the right job (as my uncle always said) and I use Adobe Lightroom on a daily basis. In this case it's not buggy, does the best at what it does and I am happy to fork over money for a product that "just works". Thanks.
Luke (not verified)
Wed, 04/03/2013 - 06:51
Permalink
Better?
To be fair Unix is under OSX the same way Unix is under Linux UI. So not much advantage to switching GUI's really especially when hes already got a Mac. If he didn't have a Mac, sure, but then he could always dual boot Linux or run it in a VM.... but he doesn't wanna ;_;
I've recently too moved to OSXs built-in tools for HP and MySQL. I've found twice sicne I did it 2 weeks ago that my local apache server stopped/crashed (I'm sure theres another word for it) but a reboot fixed that. OTherwise, its all good.
I'm going to specify a Dropbox folder as my "Sites" folder so I can develop on multiple Macs.
Danny Englander
Wed, 04/03/2013 - 10:10
Permalink
Thanks for the comments. I've
Thanks for the comments. I've actually found Mac OS X's built in Apache to be extremely stable for the most part and rarely need to restart it, only a few times over the past several months.
Interesting idea about dropbox. I mainly use Git so that mostly fixes the multiple machine issue other than the Drupal files folder which I typically exclude in gitignore.
kscheirer (not verified)
Fri, 11/09/2012 - 19:16
Permalink
also try
I replaced MAMP with Acquia's Dev Desktop a while back and couldn't be happier. They're a similar idea, but Acquia's is tuned to providing Drupal dev sites quickly and it works well for that, especially importing an already existing site. It'll create your DB, vhosts, and settings.php file for you. Like MAMP it also brings its own mysql, php and apache along, as well as drush. Just another alternative :)
Anon (not verified)
Sat, 11/10/2012 - 08:38
Permalink
You know there is a DAMP
You know there is a DAMP stack available from Acquia for free right? It comes with all of the LAMP tools run inside of its own instance so you don't have to mess with the stuff that ships with Mac OSX (think like Ruby rvm).
On top of that, it comes with compiled extensions for xDebug and other things you can enable in php.ini (5.2.x or 5.3.x- it lets you pick) and is super simple to setup. It is like MAMP pro, unlimited sites, unlimited databases. Takes about 10 minutes to setup.
Danny Englander
Sat, 11/10/2012 - 14:29
Permalink
Thanks, I will have to check
Thanks, I will have to check that out!
Bill Fitzgerald (not verified)
Sun, 11/11/2012 - 17:19
Permalink
VirtualBox
You should also look at VirtualBox - this lets you keep your Mac OS, but run as many virtual servers on your laptop as you need (and your laptop has resources to support).
This also isolates your dev environment from the rest of your work area, so you can maintain them separately.
This way, you can develop on a LAMP stack that will be identical to the eventual production environment, which helps eliminate annoying fringe-case bugs resulting from different software versions in different stacks.
Danny Englander
Mon, 11/12/2012 - 00:50
Permalink
Bill, thanks, I'll check it
Bill, thanks, I'll check it out!
Add new comment