Let's get you developing!

Getting a new development environment up and running can be a laborious process. Fortunately for you, we've eliminated all of the pain that we possibly can. :)

Unfortunately, the below instructions only apply to folks running OS X. If you aren't on a Mac, never fear! One of our intrepid instructors can still help you get set up.

Dependencies

Install the Xcode Command Lines Tools and/or full Xcode. This will grant you the most predictable behavior in building apps like MacVim.

How do you do it?

Install Xcode from the Mac App Store.
Open Xcode.
Open the Preferences window (Cmd-,).
Go to the Downloads tab.
Install the Command Line Tools.

You'll also need to create a GitHub account, if you haven't already.

Are you running on Snow Leopard? Then you'll just need to download and install this instead.

WARNING

Uninstall rvm and rbenv

If you have already installed RVM or rbenv, then you'll need to uninstall it before attempting to use these instructions. Don't remember if you installed it? Just type rvm and then rbenv into the terminal. If you see anything other than command not found, then you have them installed.

To uninstall RVM, just run the following in the terminal:

rm -rf ~/.rvm

To uninstall rbenv, just run the following in the terminal:

rbenv uninstall

Uninstall homebrew

You'll also need to uninstall homebrew, if you have already installed it (if you don't know what homebrew is, then you probably haven't). To test for the presence of homebrew, just run brew at the terminal. If you see anything other than command not found, then you have it installed. To uninstall homebrew, run the following in the terminal:

curl -L https://gist.github.com/mxcl/1173223/raw/a833ba44e7be8428d877e58640720ff43c59dbad/uninstall_homebrew.sh | sh

Don't worry, we`re about to reinstall it, along with everything else we need.

Okay, let's do this…

Now for the fun part! Head on over to this page, copy the line of text you see, and paste it into the terminal. Press enter, then wait as it asks first for your user password on OS X, and then for your GitHub username and password (maybe).

From there, sit back and relax as the script does its thing. When it's all over with, run this:

echo 'source /opt/boxen/env.sh' >> ~/.zshrc

Now you're rocking a souped up dev environment!

Optional

…but highly recommended. You should install oh-my-zsh, a package for working with the terminal, as it will make your life easier:

curl -L https://github.com/robbyrussell/oh-my-zsh/raw/master/tools/install.sh | sh

After that's finished up, run this:

echo 'source /opt/boxen/env.sh' >> ~/.zshrc

You should also install our dotfiles, which are the configuration files that control your development environment. Ours are tailored to the type of development we'll be doing at MakerSquare, and they'll keep your environment close to what we run in the lab.

There is no step 4

You're all set! Your setup is now mostly identical to the way our lab machines work.

What was installed?

Quite a number of things, actually! Here are the highlights:

Package	Purpose
homebrew	A "package manager" for OS X. Makes installing command-lines tools a snap.
git	A source code management tool.
Ruby 2.0.0-p247	The latest stable version of Ruby.
Alfred	An (awesome) quick program launcher.
SizeUp	An easy-to-use window resizer.
iTerm2	A replacement for the built-in Terminal app. Much more customizable.
zsh	A replacement for Bash, the default shell environment.
Sublime Text 2	A beautiful, easy-to-use text editor.
Mou	A Markdown text editor.
Chrome, Firefox	Web browsers. (You probably knew that.)
Dropbox	A cloud-based filesharing service.
Postgres.app	An easy way to run Postgres databases locally.

Don't worry if you already have any of this stuff - Boxen is smart enough to skip over anything that's been previously installed.

Troubleshooting

The easiest way to clear up errors on an install is to try turning it off and on again:

sudo rm -rf /opt/boxen

This will delete the boxen files entirely, allowing you to start over from the beginning. Be sure to PASTE THAT COMMAND IN EXACTLY, as mistyping it could, ya know, destroy every file on your computer.

The most likely source of pain is forgetting to source the boxen environment:

echo 'source /opt/boxen/env.sh' >> ~/.zshrc

Questions/comments/concerns? Grab an instructor and let us know! If you're not behind the Big Blue Doors, just email mike or matt [at] themakersquare.com and we'll get you squared away.

caseylang/boxen