Project

camdram

0.0
No release in over 3 years
Low commit activity in last 3 years
This gem acts as a convenient wrapper around the public API provided by a Camdram installation. See GitHub for a brief overview of available functionality and RubyDocs for more complete documentation.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 1.5
~> 12.3

Runtime

~> 2.1
~> 5.11
 Project Readme

Warning If you are viewing this README on the main branch then please note that this may contain as yet unreleased changes. You probably want to checkout a tag using the GitHub interface and view documentation for that specific version.

The Camdram Ruby Gem

Gem Version Build Status

The Camdram gem is an API wrapper and interface for Camdram 🎭 that's made with love ❤️ and written in Ruby 💎.

Installation

Add this line to your application's Gemfile:

gem 'camdram'

And then run bundle install.

Or install it yourself as:

gem install camdram

Usage

Version 2 comes with significant backend changes which now allows you to use the client credentials OAuth strategy in addition to authorisation code.

Client Credentials

Use this strategy if you are writing a server-side application that accesses the Camdram API itself or on the behalf of the user who created it.

require 'camdram/client'
client = Camdram::Client.new do |config|
  config.client_credentials(app_id, app_secret)
  config.user_agent = "MyApp v1.0.0"
  config.base_url = "https://www.camdram.net"
end

Authorisation Code

Use this strategy if you are authenticating a user via Camdram login and then acting on that user's behalf with an access token you already have from eg. omniauth-camdram. You will need a hash of the access token and optionally, if you want to refresh the token after it expires, the refresh token and Unix time when the access token expires.

require 'camdram/client'
token_hash = {access_token: "mytoken", refresh_token: nil, expires_at: nil}
client = Camdram::Client.new do |config|
  config.auth_code(token_hash, app_id, app_secret)
  config.user_agent = "MyApp v1.0.0"
  config.base_url = "https://www.camdram.net"
end

Read only

It's also possible to perform read-only requests to the Camdram API without API credentials, however this is strongly discouraged.

require 'camdram/client'
client = Camdram::Client.new do |config|
  config.read_only
  config.user_agent = "MyApp v1.0.0"
  config.base_url = "https://www.camdram.net"
end

Documentation

Full documentation is generated automatically from the source code by YARD and is available to view on RubyDocs.

Examples

Just some of the things you can do after configuring a client object:

client.user.get_shows
client.user.get_shows[0].society
client.user.get_shows[0].venue
client.user.get_shows[0].performances
client.user.get_societies
client.user.get_societies[0].name
client.user.get_societies[0].twitter_id
client.user.get_venues
client.user.get_venues[0].slug
client.user.get_venues[0].facebook_id

These public read-only actions don't require an access token (although you are still strongly advised to use one anyway):

client.get_show(6171)
client.get_show("2018-lucky")

client.get_society(1)
client.get_society("cambridge-university-amateur-dramatic-club")

client.get_venue(29)
client.get_venue("adc-theatre")

client.get_person(13865)
client.get_person("charlie-jonas")

client.get_society("cambridge-footlights").shows
client.get_society("cambridge-footlights").news
client.get_venue("cambridge-arts-theatre").shows
client.get_venue("cambridge-arts-theatre").news

It's always a good idea to handle exceptions gracefully within your application. To that end, the Camdram gem raises the following:

begin
  blargh
resuce Camdram::Error::Timeout => e
  # Handle HTTP socket and DNS lookup timeouts
rescue Camdram::Error::ClientError => e
  # Handle HTTP 4xx errors
rescue Camdram::Error::ServerError => e
  # Handle HTTP 5xx errors
rescue Camdram::Error::GenericException => e
  # Handle any other kind of error
  # (note that all of the above classes inherit from GenericException)
end

Advanced Config

Need control of the HTTP backend, timeouts, redirects, headers, logging, proxying, client certificates etc.? The Camdram gem uses the OAuth2 gem as it's backend, which in turn uses Faraday for making HTTP requests. To that end, you can pass a block when instantiating a client that will be passed to the Faraday connection builder:

require 'camdram/client'
client = Camdram::Client.new do |config|
  config.client_credentials(app_id, app_secret) do |faraday|
    faraday.request  :url_encoded          # form-encode POST params
    faraday.response :logger               # log requests to $stdout
    faraday.adapter  :patron do |session|  # make requests with Patron
      session.connect_timeout = 1
      session.timeout = 1
      session.max_redirects = 1
      session.proxy = 'hostname:8080'
      # et cetera
    end
  end
end

Be sure to checkout the documentation for Faraday and the adapter you want to use for more complex setups than the above. If you don't give any block when instantiating then the OAuth2/Faraday defaults will be used (Net::HTTP at the time of writing).

Development

First download a copy of the source code:

git clone https://github.com/CHTJonas/camdram-ruby.git && cd camdram-ruby

Once you've made a few changes you can test that things are still working as expected:

APP_ID=yourappid APP_SECRET=yourappsecret rake test

Contributing

Bug reports, enhancements and pull requests are welcome on GitHub! If you think this is something you can do yourself:

  1. Fork it ( https://github.com/CHTJonas/camdram-ruby/fork )
  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 a new Pull Request

Versioning

This library aims to adhere to Semantic Versioning 2.0.0. Violations of this scheme should be reported as bugs. Specifically, if a minor or patch version is released that breaks backward compatibility, that version should be immediately yanked and/or a new version should be immediately released that restores compatibility. Breaking changes to the public API will only be introduced with new major versions. As a result of this policy, you can (and should) specify a dependency on this gem using the Pessimistic Version Constraint with two digits of precision.

Copyright

Copyright (c) 2018 Charlie Jonas. See LICENSE for details.