Name: quimby
Owner: Stanford University Digital Library
Description: Infrastructure big picture reporting tool
Created: 2017-05-26 20:35:47.0
Updated: 2018-03-19 18:56:29.0
Pushed: 2018-02-05 23:43:00.0
Homepage: null
Size: 186
Language: Ruby
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
URL for SUL production instance:
Quimby is an infrastructure operations big picture reporting tool. It is a rails application that generates a dashboard. The dashboard presents information on servers, codebases, and analytics we can gather on the first two, for projects within SUL-DLSS and SUL-CIDR.
This is more what the application was built with; uncertain if older versions will / could work.
Clone the repository
t clone git@github.com:sul-dlss/quimby.git
Change directories into the app and install dependencies
ndle install
Create the database for the Quimby application, then migrate the schema (if needed).
ndle exec rake db:create
ndle exec rake db:migrate
Now, you want to load your data. You need to add configuration information to config/settings.yml
(see Configuration below for what is required), then run the rake task to load all data.
ter editing config/settings.yml
ndle exec rake load_data:all
This will load data from the Quimby data sources into the application database.
Finally, start the local development server:
ndle exec rails s
For each data source, you are required to have some configuration for access (captured in config/settings.yml
). For this instance of the Quimby codebase, if you want to run the load_data:all
rake task, you need the following configurations:
PUPPETDB_ENDPOINT
for making puppetdb API callsGITHUB_OAUTH_TOKEN
that allows access to the SUL-DLSS and SUL-CIDR GitHub organizations (you only need a token that allows read repository rights)HONEYBADGER_API_TOKEN
that allows you to pull project information from Honeybadger for SUL projectsGEMNASIUM_API_TOKEN
that allows you to pull Gemnasium information from the SUL Organization user in GemnasiumQuimby uses rspec for managing tests and factory girl for generating some of our fixtures class instances. To run tests:
ndle exec rake
Quimby uses capistrano to deploy. Current it's deployed to a staging machine named sul-quimby-stage
and deployed via:
ndle exec cap stage deploy
config/deploy/ENV.rb
exist[a-z0-9-]+.stanford.edu/
in each environment config fileCapfile
exists in the repository.travis.yml
exists in the repositoryconfig/initializers/okcomputer.rb
exists in the repositoryconfig/initializers/is_it_working.rb
exists in the repositoryhoneybadger
is in the Gemfile in the repositorycapistrano/honeybadger
in the Capfile
coveralls
is in the Gemfile in the repositoryrails
is in the Gemfile in the repositorygemspec
exists somewhere in the repositorycurrent: FALSE