Automatic development environment setup for Locker
Switch branches/tags
Nothing to show
Pull request Compare This branch is 3 commits ahead of pib:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


LockerBox is a small script to get you up and running with Locker as quickly and easily as possible, without having to spend a lot of time or effort getting all the dependencies set up.

At the moment, this is more intended for developers who want to evaluate Locker than end users. However, this could be a first step toward a system for building end-user packages of Locker.


There are only three or four things that are needed in order to get Locker up and running using LockerBox:

  • Python 2.6+

  • Git

  • A C++ build environment (Make, a C++ compiler, and libssl)

  • Node.js v0.4.6+ (optional)

If you don't already have Node.js 0.4.8+ installed, it will be built for you, and installed in the lockerbox directory. How long this takes will depend on your machine.

Any other dependencies will be automatically downloaded and installed into lockerbox/local, including:

Of course, if you already have recent enough versions of Node.js, npm, virtualenv, and MongoDB installed, they won't be re-installed locally. Instead, the already-installed versions will be used.


Just run:


Or if you don't want to download first:

curl | sh

The second option will create a directory called "lockerbox" and put everything there. The first will run in the current directory (which makes sense if you've just checked out the repo).

Either way, as soon as everything needed is downloaded and started, Locker should be up and running, and you can visit localhost:8042 to see your running copy of Locker.

The next time you run, it won't need to install anything, it will just check that it's all there, and then launch Locker.

And then?

At this point, you should have a copy of Locker in lockerbox/Locker. Now start hacking away!

If something in your environment gets messed up somehow, you can always blow away lockerbox/local and/or lockerbox/Locker and they will be auto-filled with dependencies again the next time is run.