Maslow - how to spin up the GOV.UK Needs API

Caveat: This post should’ve been written back in October 2014 but life got in the way and I’ve forgotten most of it, however, like all good developers I wrote myself some great documentation (not) so this should be a breeze right? (possibly not). Either way, I’ll try and make it easy to follow!

To bring you up to speed, GDS built an application called Maslow to capture and manage the user needs that GOV.UK is designed to meet. I’m sure someone from GDS can correct me on such an underwealming description but regardless, it’s a really smart idea and something I hope can be adopted or replicated elsewhere across the public sector.

I appreciate GDS have never intended for their code to be used like an open source project and have far higher priorities than writing documentation for morons like me so here’s my brief-ish guide to getting up and running with Maslow.


This guide assumes:

Step 1: Clone Maslow

We may aswell start simple right?

Depending on your intentions you can either clone Maslow directly using the command below head over to the Maslow repository, fork it yourself. Either way, make sure you get a copy on your machine.

git clone

Once you’ve done that, give yourself a pat on the back - first job, done.

Step 2: Clone the Need API

Maslow depends on having a running instance of the GOV.UK Need API. Thankfully the Need API is pretty straightforward itself so head on over and grab yourself a copy, you can use the command below or the GOV.UK Need API repository

git clone

Sweet job, we now have the GOV.UK Need API on our machine.

Step 3: Starting the Need API

Now we have the Need API and Maslow locally, we can start the process of getting them up and running.

The Github page for the Need API says the dependencies are:

You’ll need to install both of those. While you’re there, what they don’t tell you is that Redis is also required, go ahead and install that too. (I know right?)

All installed? Move on…

Step 4: Getting dependencies running

In a new terminal window, head to your Elasticsearch install and start it up:


Oh and we’ll also need to have Mongo running, start mongo in a new terminal window using:


Almost there, open another window and get Redis running:


At this point we should be okay to run the Need API itself, open another terminal window, change directories until you’re in your govuk_need_api directory and hit:

bundle exec unicorn -p 3000

All being well you should be able to visit http://localhost:3000 and have a screen that looks a little like the one below.

GDS's Need API application running locally in devleopment mode

If you get this far, tweet me and I’ll work out some sort of prize/badge/hug type deal, points for persistance.

Right, now we have the GOV.UK Need API running, we can get attempt to Maslow running too.

Step 5: Getting Maslow running

Now, you would hope that you could just follow the instructions on the Github readme page, no such luck unfortunately. What I mean to say is, you can, but it probably won’t work.

In short, Maslow has an object reference to the Need API. I don’t know nearly enough about ruby or rails to know exactly how it works, I’m still learning but to get up and running, open up the following file:

~maslow: config\initializers\gds_api.rb

On about line 5, you’ll see the following:

Maslow.need_api ='need-api'),

Swap it for this:

Maslow.need_api ='http://localhost:3000/',

All we’re doing is swapping out the reference to Plek, GDS’s internal dns lookup, for a hardcoded reference to our local instance of the Need API, running on port 3000.

Sidenote: you can set an environment variable and use Plek itself but this is the quick and dirty method that’ll get you moving quicker - no one needs hassle right?

Step 6: The home straight

One final thing before we start Maslow…

We’re not using the GDS authorisation platform so Maslow seeds the database with a user for us. Awesome right?

The annoying thing is, unless we make a change, all you’ll get is permission to sign-in to Maslow, you won’t get any permissions to create or update needs or do anything of any real use.

So one final thing, updating the user permissions of the default user:

Head to:

~maslow: db\seeds.rb

and find the line that defines the users permissions:

@user.permissions = ["signin"]

change that to

@user.permissions = ["signin","admin","editor"]

Excellent, now we can fire it up!

Fire it up!

Now you should be able to fire up Maslow, open one final new terminal window and head into the directory where you’ve cloned maslow then run:

bundle exec unicorn -p 3001

All being well, you should now have Maslow up and running on your local machine, it’ll look something like this:

GDS's Maslow application running locally in devleopment mode

That’s it! If you got this far, bravo. I’m amazed I did. I have pushed this a bit further and got a bunch of local authorities loaded instead of the central government departments from Whitehall but I need to revisit how I ended up doing that to be honest as it was horrendously hacky. As I say, my ruby knowledge is pretty limited, I’ve just hacked my way through error messages until this point.

GDS have far more important things to do than document how their stuff works so hopefully this goes some way to appeasing that frustration - if anyone else has got GOV.UK code up and running elsewhere, please let me know!