Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Ruby CSS Other
Latest commit 08b7163 @dsingleton dsingleton Merge pull request #22 from gds-attic/mattbostock-patch-1
Correct copyright notice
Failed to load latest commit information.
app Bump gds-sso to 9.3.0
db Bump gds-sso to 9.3.0
doc Initial commit. Rails 3.1 app with a couple of handy models
lib Remove directgov links and existing services from the needs CSV export
log Initial commit. Rails 3.1 app with a couple of handy models
public Remove existing assets
script Cucumber. Installed
spec Redesign need pages using Bootstrap
vendor Move datatables out of the vendor folder and load it on every page
.gitignore Ignore oauth credentials initialiser when working out git status
.rspec RSpec. Installed
.ruby-version Bump ruby version
.rvmrc Drop use of gemset
Gemfile Bump gds-sso to 9.3.0
Gemfile.lock Bump gds-sso to 9.3.0
LICENCE.txt Correct copyright notice Add permission setting to example code in README
Rakefile Correctly display timestamps Initial commit. Rails 3.1 app with a couple of handy models Run migrations too Added gds-warmup-adapters

Welcome to Need-o-Tron

For an overview of the need-o-tron visit Richard Pope's introductory blog post

Getting set up

Need-o-Tron is a Rails 3.2 application. It is built with ruby 1.9.2 and is only guaranteed to work with that and 1.9.3, though it should be compatible with ruby 2.0

To get up and running you'll need mysql, elasticsearch, ruby and bundler installed. On a mac we recommend using homebrew to install the former two.

Once those requirements are satisfied, getting the app up and running should just be a case of running:

bundle install
rake db:setup
rails server


Need-o-tron designed to work as part of a suite of applications, authenticating against an OAuth provider such as Sign-on-o-tron

It does that via the GDS-SSO gem. See that project's README for configuration details. It's an OAuth2 provider, and you could alternatively use any other OAuth2 provider.

If you don't want to authenticate against a separate app there's also a basic strategy for development use that will simply use the first user in your database. To set that up you'll want something like:

% rails console
u = => 'First User', :email => '', :uid => 1)
u.permissions = ["signin", "admin"]

Something went wrong with that request. Please try again.