The public Travis API
Go to file
2013-05-02 20:06:19 +02:00
config
docs
lib merging stuff and fun 2013-05-02 20:06:19 +02:00
public Add favicon 2013-04-15 02:17:08 -05:00
script Revert "switch to unicorn" 2013-04-16 20:03:47 +02:00
spec fix specs 2013-04-24 16:59:26 +02:00
.buildpacks
.gitignore
.travis.yml
config.ru Fix newrelic 2013-04-17 23:44:51 +02:00
CONTRIBUTING.md
Gemfile i wonder what i am doing wrong with octopus 2013-05-02 17:08:31 +02:00
Gemfile.lock i wonder what i am doing wrong with octopus 2013-05-02 17:08:31 +02:00
Procfile
Rakefile Don't error out on micro migrations on production 2013-03-27 15:13:19 +01:00
README.md
travis-api.gemspec fix specs 2013-04-24 16:59:26 +02:00

The public Travis API

This is the app running on https://api.travis-ci.org/

Installation

Setup:

$ bundle install

Run tests:

$ RAILS_ENV=test rake db:create db:schema:load
$ rake spec

Run the server:

$ rake db:create db:schema:load
$ foreman start

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

API documentation

We use source code comments to add documentation. If the server is running, you can browse an HTML documenation at /docs.

Project architecture

lib
`-- travis
    `-- api
        `-- app
            |-- endpoint    # API endpoints
            |-- extensions  # Sinatra extensions
            |-- helpers     # Sinatra helpers
            `-- middleware  # Rack middleware

Classes inheriting from Endpoint or Middleware, they will automatically be set up properly.

Each endpoint class gets mapped to a prefix, which defaults to the snake-case class name (i.e. Travis::Api::App::Profile will map to /profile). It can be overridden by setting :prefix:

require 'travis/api/app'

class Travis::Api::App
  class MyRouts < Endpoint
    set :prefix, '/awesome'
  end
end