So, here I was trying to setup Vagrant on my Mac. Everything went fine till the vagrant up command and boom: myfirstvagrantproject $ vagrant up Bringing machine 'projectname' up with 'virtualbox' provider... ==> projectname: The cookbook path '/Users/cruisemaniac/.berkshelf/projectname/vagrant/berkshelf-20140909-37664-1gf5t34-projectname' doesn't exist. Ignoring... Updating Vagrant's berkshelf: '/Users/cruisemaniac/.berkshelf/projectname/vagrant/berkshelf-20140909-37664-1gf5t34-projectname' RuntimeError: Couldn't determine Berks version: #<Buff::ShellOut::Response:0x00000101040360 @exitstatus=1, @stdout="", @stderr="/Users/cruisemaniac/.rbenv/versions/2.1.2/lib/ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find 'berkshelf' (>= 0) among 56 total gem(s) (Gem::LoadError)\n\tfrom /Users/cruisemaniac/.rbenv/versions/2.1.2/lib/ruby/2.1.0/rubygems/dependency.rb:309:in `to_spec'\n\tfrom /Users/cruisemaniac/.rbenv/versions/2.1.2/lib/ruby/2.1.0/rubygems/core_ext/kernel_gem.rb:53:in `gem'\n\tfrom /Users/cruisemaniac/. Read more

I was recently trying to setup MySQL with Homebrew and noticed that the mysql server that brew installed was not playing nice with the existing setups. The solution is to wipe out any existing MySQL installs you’ve got on your mac and redo everything from scratch with brew. This makes the mysql installed from Brew your main installation. Read up on this blogpost that details the sequence. 5 minutes, a few commands and all is hanky-panky in mysql land :-) Read more