When developing for the web, I like to make sure that the software I'm using in development is a close match for the code that I'm running on my live servers.
- After MySQL dmg installation if there is an issue with the MySQL PATH when mysql commands are run, add PATH to.bashprofile (if you are using bash) $ mysql -version -bash: mysql: command not found $ $ vim /.bashprofile.
- The world's most popular open source database MySQL.com; Downloads; Documentation; Developer Zone; Developer Zone Documentation MySQL.com.
My preferred approach is to develop my code in a virtual machine containing the same operating system and software as my production server environment, but sometimes we don't have much control over the code we run on the server. This is often the case when hosting apps on a PaaS (Platform as a Service) provider such as Heroku.
I'm trying to setup up MySQL on mac os 10.6 using Homebrew by brew install mysql 5.1.52. Everything goes well and I am also successful with the mysqlinstalldb. However when I try to connect to the. Mysql for mac downloaded from mysql.com, not homebrew version – Mohamed Sameer Nov 14 '17 at 5:10 1 @tadman where i want to run this find command?
I develop Agile Planner on a Mac, and install software required by my app (such as PostgreSQL, memcached and Elasticsearch) using the homebrew package manager.
Packages in homebrew are typically updated to provide the latest version of an app, which means that you can find yourself running more recent versions of your software in development, than in production.
It's useful to be able to install a specific version.
It's easy to do with homebrew.
Installing from a tap
If a lot of people might need to use an old version of a package (or 'formula', in homebrew's terminology), it might have been made available as a tap. Old versions are maintained in the homebrew-versions repository, and show up in the output of
homebrew search
:The first line of output refers to the default package, while the following line refers to the 'tapped' versions that are also available. You can install one of them like this:
In my case, the version I'm looking for (version 1.2.1) isn't available as a tap, so I need an alternative approach.
Installing from a specific commit
The homebrew formulae (that tells the
brew
command how to build each package) are all stored in a Git repository.All we need to do is to roll back the formula for the package we want to build to the latest commit that was active for that package.
Up until around October 2014, Homebrew had a
brew versions
command that would list all the versions of a package, and the corresponding Git commands to roll the formula back.If your version of homebrew is more recent than October 2014, you'll need to install the
boneyard
tap in order to make the command available:Then you can run
brew versions
. Here's the first few lines of output for Elasticsearch:There's more information on the
brew versions
command in this StackOverflow answer, so if at some point in the future you find that this blog post seems to be out of date, try that.So anyway, back to installing Elasticsearch. I need version 1.2.1, so I'll pipe the versions command through grep and then run the Git command:
If you've already got a version of the package you're building installed, you might need to unlink it before installing it:
I love feedback and questions — please get in touch on Twitter orleave a comment.
![Mac brew install mysql Mac brew install mysql](/uploads/1/1/9/6/119673851/343056622.png)
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
#
):Restart Apache:
Install MySQL
- 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
mysql
and mysqladmin
. However there are other commands that are helpful such as mysqldump
. Instead, I updated my path to include /usr/local/mysql/bin
.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:
Creating VirtualHosts
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:
Download Homebrew
Now Apache will load httpd-vhosts.conf. Let's edit this file.
Here is an example of VirtualHosts I've created.
The first
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.Mac Homebrew Tutorial
The second
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.
Mysql Mac Brew
Restart Apache:
Mac Brew Install Mysql
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.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.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: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.
Install PHPMyAdmin
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.
Closing
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.