Posted By: Keith Combs | Dec 29th, 2008 @ 8:26 AM | 25,353 Views | 1 Comment
Why on earth would you run the LAMP stack on Windows?  Well for one thing LAMP commonly refers to Linux, Apache, MySQL and PHP.  So running LAMP on Windows Server 2008 really means running it in a virtual machine and the only supported method for doing that at the moment is via SUSE Enterprise Server from Novell.  This was discussed on the webcast I delivered today that more broadly discusses running Open Source Software (OSS) on Windows Server with IIS7.

In order to take one or more open source applications to the Windows platform, you might choose the prudent and safe route.  First running the entire LAMP stack in a VM.  Next, you might decide to remove the L and run the AMP portions on Windows Server 2008.  That's where the meat of the webcast I did today really starts.  You'll see in the second webcast demo we install Apache.  Later we install PHP, MySQL then Drupal on top of all of that.

The purpose of the webcast is to highlight the migration and coexistence that is possible.  You don't have to totally tear everything you know and love down and replace it.  Windows Server 2008 will be happy to run Apache, MySQL and PHP.  If you decide to replace pieces of that solution over time, you can do so pretty easily and that is demonstrated in the webcast replay.

I decided to record a higher fidelity version of some of the demos and instead of using the Drupal software used in the webcast, I used a common blogging software product called Wordpress.  So here is Part 2 on installing MySQL.

See my blog post at http://blogs.technet.com/keithcombs/archive/2008/12/16/running-lamp-on-windows-server-2008-webcast-and-screencasts-now-available.aspx for more information.

Rating:
0
0
Dodo
Dodo
I'm your creativity creator™ :)
Just clicking next everywhere might be fine, but you definitely should use UTF-8 as the default character set for your databases. Going with the setup's default (Latin-1) might be bad for foreign characters and most open source scripts forget to include the mySQL statement to use a character set when creating tables.

PS: there's a typo in Windows Wink
Microsoft Communities