The first thing I did after installing MAMP PRO is change the default ports of Apache and mySQL.
Apache = Port 80
MySQL = Port 3306
That way, I don’t have to type port numbers during my testing… i.e. localhost:8080
(Remember, I’m trying to make this as easy as possible.)
Running the Apache/MySQL server as user “www/mysql”. Make sure this is selected in your MAMP Pro General settings.
I also changed the MySQL Root Password to my own password.
For PHP, MAMP offers (2) versions of PHP.
5.2.13
5.3.2
I don’t know what’s the significance of this… I selected 5.3.2 since this is the latest version.
Cache is OFF, and Zend Optimizer checkbox in unchecked. I don’t know what Zend is and how this is relevant to PHP. If someone can explain it to me briefly, without getting too much technical with me, please let me know.
Under Postfix, I entered the domain of my outgoing mail… also checked the box Smart Host and entered my Hostname, User Name, and Password. Authentication type I have 2 choices.. Plain Text and MD5 Challenge-Response. I tried both authentication types, and both worked for sending out mail… so <shrug> I just selected Plain Text.
The next step I did is create a “host”… select the Hosts button on MAMP Pro. I used “testsite.com” as my domain for testing. Note: You don’t have to register this domain name at Godaddy… this is just for your internal use. You can name it anything you want. For me, I selected “testsite.com”. Check the box called “Local name resolution”
On my Macintosh HD, I created a subdirectory on the root called “VirtualHosts”… then a subdirectory inside that called “TestSite”.
So basically, if I type “testsite.com” on my browser, it will execute files located in the directory “/VirtualHosts/TestSite”. This subdirectory will be my playground.
On your Dreamweaver, or HTML editor program, save all your work in the TestSite subdirectory.
I have to tell you, I really like this setup. Being able to do development on your own workstation machine instead of copying/ftping files to a server. It just made learning PHP much more efficient and faster.
Before, the workflow was like this:
Edit file
FTP and Upload file to Apache server
Test using web browser
if error, go back and edit file.
Repeat…
Now, my workflow is like this:
Edit file on Macintosh HD
FTP and Upload file to Apache server
Test using web browser
if error, go back and edit file
Repeat…
I only removed a single step (ftping and uploading the file), but it just makes for a more faster workflow… which is conducive when you’re learning a new language and playing around with it.