The MAMP package includes the Apache web server, PHP engine, and MySQL database. Mac OS X 10.5 and later include the MySQL database and Apache server with PHP support. While it certainly is possible to configure the built-in database and server with the IDE, MAMP’s all-in-one bundle provides a convenient and easily configurable solution. Apache, MySQL, PHP. This is repository with documentation of MAMP server installation in OS X 10.8. I use this configuration on my Mac Book (jozef-mbp).
Get your Local Web Development Environment Up & Running on macOS Sierra
With Apples’ new macOS Sierra now in public beta, here is how to get the AMP stack up and running on the new macOS. This tutorialwill go through the process on getting Apache, MySQL, PHP (or otherwise known as the ‘AMP’ stack)and phpMyAdmin running on the new mac OS Sierra.
For Mac OS The package has been set up to be very easy to install and to use like Windows OS. To install and run it on Mac OS download offline installer setup. It is an easy to install Apache distribution for Mac OS X. The package for Mac is similar to windows. It includes the Apache web server, MySQL, PHP, Perl, an FTP server and phpMyAdmin.
- Mac OS X 10.6 Snow Leopard comes with Apache and PHP (Apache/2.2.17 (Unix) modssl/2.2.17 OpenSSL/0.9.8l DAV/2 PHP/5.3.4), so it is quite easy to setup a MAMP server. Sure, there are other ways to do the MAMP setup: Build Apache, MySQL and PHP from sources.
- MacOS 10/15 Catalina Apache Setup: MySQL, Xdebug & More Official home of Grav CMS. How to Install Apache, PHP, MySQL & phpMyAdmin on macOS. Create the database schema On the Home screen for the MySQL Workbench, in the SQL Development section, double-click the database connection that you created when you created the server instance for the.
This tutorial sets up the AMP stack in more of a traditional way using the loaded Apache and PHP and downloading MySQL and phpMyAdmin.
Setting Stuff Up
Web serving is possible via the inbuilt Apache app, it is installed ready to be fired up.
This needs to be done in the Terminal which is found at /Applications/Utilities/Terminal
For those not familiar with the Terminal, it really isn’t as intimidating as you may think, once launched you are faced with a command prompt waiting for your commands – just type/paste in a command and hit enter, some commands give you no response – it just means the command is done, other commands give you feedback.
Using the prefix of sudo is required for commands that have their applications protected in certain folders – when using sudo you will need to confirm with your admin password or iCloud password if set up that way…. lets get to it….
to start Apache web sharing
to stop it
to restart it
To find the Apache version
The Apache version that comes in macOS Sierra is Apache/2.4.23
After starting Apache – test to see if the webserver is working in the browser – http://localhost – you should see the “It Works!” text.
If you don’t get the localhost test, you can try troubleshooting Apache to see if there is anything wrong in its config file by running
This will give you an indication of what might be wrong.
Document root is the location where the files are shared from the file system and is similar to the traditional names of ‘public_html‘ and ‘htdocs‘, OSX has historically had 2 web roots one at a system level and one at a user level – you can set both up or just run with one, the user level one allows multiple accounts to have their own web root whilst the system one is global for all users. It seems there is less effort from Apple in continuing with the user level one but it still can be set up with a couple of extra tweaks in configuration files. It is easier to use the user level one as you don’t have to keep on authenticating as an admin user.
System Level Web Root
– the default system document root is still found at –
The files are shared in the filing system at –
User Level Root
The other web root directory which is missing by default is the ‘~/Sites’ folder in the User account. This takes a bit longer to set up but some users are very accustomed to using it.
You need to make a “Sites” folder at the root level of your account and then it will work. Once you make the Sites folder you will notice that it has a unique icon which is a throwback from a few versions older. Make that folder before you set up the user configuration file described next.
You have to make a few additional tweaks to get the ~/Sites folder back up and running.
Add a “username.conf” filed under:
If you don’t already have one (very likely), then create one named by the short username of the account with the suffix .conf, its location and permissions/ownership is best tackled by using the Terminal, the text editor ‘nano‘ would be the best tool to deal with this.
Launch Terminal, (Applications/Utilities), and follow the commands below, first one gets you to the right spot, 2nd one cracks open the text editor on the command line (swap ‘username‘ with your account’s shortname, if you don’t know your account shortname type ‘whoami‘ the Terminal prompt):
Then add the content below swapping in your ‘username’ in the code below:
Permissions on the file should be:
If not you need to change…
Open the main httpd.conf and allow some modules:
And make sure these modules are uncommented (the first 2 should already be on a clean install):
Whilst you have this file open also to get php running uncomment. (Mentioned also in the PHP part of the article).
And also uncomment this configuration file also in httpd.conf – which allows user home directories.
Save all your changes (Control + O in nano)
Then open another Apache config file and uncomment another file:
Save all your changes (Control + O in nano)
Restart Apache for the new file to be read:
Then this user level document root will be viewable at:
You should only see a directory tree like structure if the folder is empty.
Override .htaccess and allow URL Rewrites
If you are going to use the web serving document root at /Library/WebServer/Documents it is a good idea to allow any .htaccess files used to override the default settings – this can be accomplished by editing the httpd.conf file at line 217 and setting the AllowOverride to All and then restart Apache. This is already taken care of at the Sites level webroot by following the previous step.
Also whilst here allow URL rewrites so your permalinks look clean not ugly.
Uncomment in httpd.conf – should be uncommented on a clean install.
PHP 5.6.24 is loaded in the build of macOS Sierra and needs to be turned on by uncommenting a line in the httpd.conf file.
Use “control” + “w” to search within nano and search for ‘php’ this will land you on the right line then uncomment the line (remove the #):
Write out and Save using the nano short cut keys at the bottom ‘control o’ and ‘control x’
Reload apache to kick in
To see and test PHP, create a file name it “phpinfo.php” and file it in your document root with the contents below, then view it in a browser.
The macOS Sierra Public Beta’s didn’t play well with MySQL 5.7.x, but these issues are now resolved by using MySQL 5.7.16
MySQL doesn’t come pre-loaded with macOS Sierra and needs to be dowloaded from the MySQL site.
The latest version of MySQL 5.7.16 does work with the public release of macOS.
If you already have MySQL 5.7 and you have upgraded OS from El Capitan to Sierra I expect that to be ok, but will be interested if anyone comments on that.
Use the Mac OS X 10.11 (x86, 64-bit), DMG Archive version (works on macOS Sierra).
If you are upgrading from a previous OSX and have an older MySQL version you do not have to update it. One thing with MySQL upgrades always take a data dump of your database in case things go south and before you upgrade to macOS Sierra make sure your MySQL Server is not running.
When downloading you don’t have to sign up, look for » No thanks, just take me to the downloads! – go straight to the download mirrors and download the software from a mirror which is closest to you.
Once downloaded open the .dmg and run the installer.
When it is finished installing you get a dialog box with a temporary mysql root password – that is a MySQL root password not a macOS admin password, copy and paste it so you can use it. But I have found that the temporary password is pretty much useless so we’ll need to change it straight away.
You are also told:
If you lose this password, please consult the section How to Reset the Root Password in the MySQL reference manual.
Change the MySQL root password
Note that this is not the same as the root or admin password of macOS – this is a unique password for the mysql root user, use one and remember/jot down somewhere what it is.
Start it in safe mode:
This will be an ongoing command until the process is finished so open another shell/terminal window, and log in without a password as root:
Change the lowercase ‘MyNewPass’ to what you want – and keep the single quotes.
You can then start the MySQL server from the System Preferences or via the command line.
Command line start MySQL.
To find the MySQL version from the terminal, type at the prompt:
This also puts you in to a shell interactive dialogue with mySQL, type q to exit.
After installation, in order to use mysql commands without typing the full path to the commands you need to add the mysql directory to your shell path, (optional step) this is done in your “.bash_profile” file in your home directory, if you don’t have that file just create it using vi or nano:
The first command brings you to your home directory and opens the .bash_profile file or creates a new one if it doesn’t exist, then add in the line above which adds the mysql binary path to commands that you can run. Exit the file with type “control + x” and when prompted save the change by typing “y”. Last thing to do here is to reload the shell for the above to work straight away.
You will get the version number again, just type “q” to exit.
Fix the 2002 MySQL Socket error
Fix the looming 2002 socket error – which is linking where MySQL places the socket and where macOS thinks it should be, MySQL puts it in /tmp and macOS looks for it in /var/mysql the socket is a type of file that allows mysql client/server communication.
First fix the 2002 socket error if you haven’t done so from the MySQL section-
Download phpMyAdmin, the zip English package will suit a lot of users, then unzip it and move the folder with its contents into the document root level renaming folder to ‘phpmyadmin’.
Make the config folder
Change the permissions
Run the set up in the browser
You need to create a new localhost mysql server connection, click new server.
Switch to the Authentication tab and set the local mysql root user and the password.
Add in the username “root” (maybe already populated, add in the password that you set up earlier for the MySQL root user set up, click on save and you are returned to the previous screen.
(This is not the macOS Admin or root password – it is the MySQL root user).
Make sure you click on save, then a config.inc.php is now in the /config directory of phpmyadmin directory, move this file to the root level of /phpmyadmin and then remove the now empty /config directory.
Now going to http://localhost/~username/phpmyadmin/ will now allow you to interact with your MySQL databases.
To upgrade phpmyadmin just download the latest version and copy the older ‘config.inc.php‘ from the existing directory into the new folder and replace – backup the older one just in case.
To run a website with no permission issues it is best to set the web root and its contents to be writeable by all, since it’s a local development it shouldn’t be a security issue.
Lets say that you have a site in the User Sites folder at the following location ~/Sites/testsite you would set it to be writeable like so:
If you are concerned about security then instead of making it world writeable you can set the owner to be Apache _www but when working on files you would have to authenticate more as admin you are “not” the owner, you would do this like so:
This will set the contents recursively to be owned by the Apache user.
If you had the website stored at the System level Document root at say /Library/WebServer/Documents/testsite then it would have to be the latter:
Another easier way to do this if you have a one user workstation is to change the Apache web user from _www to your account.
That’s it! You now have the native AMP stack running on top of macOS Sierra.
macOS Update: While these instructions still work, there are new posts for recent versions of macOS, the latest being Install Apache, PHP, and MySQL on macOS Mojave.
I have installed Apache, PHP, and MySQL on Mac OS X since Leopard. Each time doing so by hand. Each version of Mac OS X having some minor difference. This post serves as much for my own record as to outline how to install Apache, MySQL, and PHP for a local development environment on Mac OS X
Mountain Lion Mavericks.
I am aware of the several packages available, notably MAMP. These packages help get you started quickly. But they forego the learning experience and, as most developers report, eventually break. Personally, the choice to do it myself has proven invaluable.
It is important to remember Mac OS X runs atop UNIX. So all of these technologies install easily on Mac OS X. Furthermore, Apache and PHP are included by default. In the end, you only install MySQL then simply turn everything on.
First, open Terminal and switch to
root to avoid permission issues while running these commands.
Enable Apache on Mac OS X
Note: Prior to Mountain Lion this was an option for Web Sharing in System Prefrences → Sharing.
Verify It works! by accessing http://localhost
Enable PHP for Apache
OS X Mavericks Update: You will need to rerun the steps in this section after upgrading an existing install to Mac OS X Mavericks.
First, make a backup of the default Apache configuration. This is good practice and serves as a comparison against future versions of Mac OS X.
Now edit the Apache configuration. Feel free to use TextEdit if you are not familiar with vi.
Uncomment the following line (remove
- Download the MySQL DMG for Mac OS X
- Install MySQL
- Install Preference Pane
- Open System Preferences → MySQL
- Ensure the MySQL Server is running
- Optionally, you can enable MySQL to start automatically. I do.
The README also suggests creating aliases for
mysqladmin. However there are other commands that are helpful such as
mysqldump. Instead, I updated my path to include
Note: You will need to open a new Terminal window or run the command above for your path to update.
I also run
mysql_secure_installation. While this isn't necessary, it's good practice.
Connect PHP and MySQL
You need to ensure PHP and MySQL can communicate with one another. There are several options to do so. I do the following:
You could stop here. PHP, MySQL, and Apache are all running. However, all of your sites would have URLs like http://localhost/somesite/ pointing to /Library/WebServer/Documents/somesite. Not ideal for a local development environment.
OS X Mavericks Update: You will need to rerun the steps below to uncomment the vhost
Include after upgrading an existing install to Mac OS X Mavericks.
To run sites individually you need to enable VirtualHosts. To do so, we'll edit the Apache Configuration again.
Uncomment the following line:
Now Apache will load httpd-vhosts.conf. Let's edit this file.
Here is an example of VirtualHosts I've created.
VirtualHost points to
/Library/WebServer/Documents. The first
VirtualHost is important as it behaves like the default Apache configuration and used when no others match.
VirtualHost points to my dev workspace and I can access it directly from http://jason.local. For ease of development, I also configured some custom logs.
Note: I use the extension local. This avoids conflicts with any real extensions and serves as a reminder I'm in my local environment.
In order to access http://jason.local, you need to edit your hosts file.
Add the following line to the bottom:
I run the following to clear the local DNS cache:
Now you can access http://jason.local.
Note: You will need to create a new
VirtualHost and edit your hosts file each time you make a new local site.
Artlantis Studio 2019 Crack & Serial Number Full Free Download Artlantis Studio 2019 Crack with Serial Number is the fastest stand-alone 3D rendering software developed especially for architects and designers, ideal for quickly and easily creating high resolution 3D renderings, QuickTime VR Panoramas, Objects and animations. Artlantis Studio 5 Crack To create stunning images, Artlantis Studio 5 Crack now includes its own built-in physics engine, emphasizing the physical quality of representation, precision, accuracy equipment and energy conservation. Anime Studio Pro 10 Crack is an other software for same work. White balance Artlantis Studio 5 Crack. Artlantis Studio 126.96.36.199 (x64) Multilingual + Crack by Up7-TEAM 558.38 MB. Information: The new, physically correct Artlantis 7 rendering engine, with its legendary simplicity, allows you to create visualizations of incomparable beauty and quality. Artlantis is a family of stand-alone rendering applications developed for architects and designers. Artlantis 2020 Crack + Serial Key (Latest) Download. Artlantis Studio Crack i n terms of lighting, the software offers excellent quality effects, imitating various natural and artificial sources, such as the sun, sky or an ordinary light bulb. You can fully adjust the size, position, and angle of the light source, allowing it to fall where you. Artlantis Studio 8.0.2 B22044 Crack. Download Complete Setup Artlantis Studio 8.0.2 B22044 Crack Full Version with License Code. Artlantis Studio is animation creating plus visual production – compatible with 3D modeling, easily developing your. Artlantis studio for mac crack.
A note about permissions
You may receive 403 Forbidden when you visit your local site. This is likely a permissions issue. Simply put, the Apache user (
_www) needs to have access to read, and sometimes write, your web directory.
Apache Mysql Php For Mac Os Xp
If you are not familiar with permissions, read more. For now though, the easiest thing to do is ensure your web directory has permissions of
755. You can change permissions with the command:
Apache Mysql Php For Mac Os X 10.10
In my case, all my files were under my local
~/Documents directory. Which by default is only readable by me. So I had to change permissions for my web directory all the way up to
~/Documents to resolve the 403 Forbidden issue.
Note: There are many ways to solve permission issues. I have provided this as the easiest solution, not the best.
Unless you want to administer MySQL from the command line, I recommend installing PHPMyAdmin. I won't go into the details. Read the installation guide for more information. I install utility applications in the default directory. That way I can access them under, in this case, http://localhost/phpmyadmin.
A local development environment is a mandatory part of the Software Development Process. Given the ease at which you can install Apache, PHP, and MySQL on Mac OS X there really is no excuse.
Find this interesting? Let's continue the conversation on Twitter.