doesfacebook 0.6.0 → 1.0.0.pre1

data/CHANGELOG.rdoc

@@ -0,0 +1,49 @@
+= DoesFacebook Change Log
+
+This document details notable changes between versions in the gem.
+
+=== v1.0.0 (this version)
+
+
+=== v0.6.0 / Oct 11 2012
+
+* Add proper ActiveSupport deprecation warnings for deprecated methods and configuration
+
+=== v0.5.5 / May 18 2012
+* Add sessionify_signed_parameter filter for signed_request management on non-POSTed, subsequent requests within iframes
+* Add opts parameter to does_facebook invocation with support for toggling :session behavior
+* Documentation updates for session switch on does_facebook invocation
+
+=== v0.5.4 / Apr 30 2012
+* Middleware fix for first-strike page loads
+
+=== v0.5.3 / Apr 23 2012
+* Middleware POST rewrite now performed on requests from Facebook only
+ 
+=== v0.5.2 / Apr 04 2012
+* Additional fix for SSL/HTTPS configuration loader
+ 
+=== v0.5.1 / Apr 04 2012
+* Fix for SSL/HTTPS configuration loader logic
+ 
+=== v0.5.0 / Mar 28 2012
+* Configuration loader completely rewritten, is now request URL based
+* Configuration logging messages streamlined
+ 
+=== v0.5.0.pre / Winter 2012 (various "pre" versions)
+* "namespace" configuration key adopted replacing "canvas_name"
+* "canvas_name" configuration key deprecated (still supported, but triggers deprecation logger message)
+* app_namespace helper replaces app_canvas_name helper
+* url_for_canvas, link_to_canvas updated to use namespace
+* Documentation updates for changes to configuration
+* fb_init() helper added for FBJS invocation with app properties
+* AJAX, xhr requests are passed through Middleware POST rewrite
+* Remove api_key helpers, support (field long deprecated by Facebook)
+* Remove api_key configuration key from doesfacebook.yml
+* Add Rack Middleware rewriting POST requests to appropriate methods when signed_request is present
+
+=== v0.4.3 / Sep 18 2011
+* Add support for SSL/HTTPS configured apps with "ssl_callback_url" configuration key
+* Update to url_for_canvas, link_to_canvas, redirect helpers to support SSL/HTTPS configured applications
+
+

data/Gemfile

@@ -0,0 +1,21 @@
+# DOES FACEBOOK
+# Gemfile
+
+source "http://rubygems.org"
+
+# Runtime dependencies:
+
+# This gem adds functionality to Rails applications:
+gem "rails", ">= 3.2.0"
+
+
+# Development dependencies:
+group :development do
+  gem "bundler", ">= 1.1"
+  gem "jeweler", "~> 1.8.4"
+  gem "rdoc", "~> 3.12"
+  gem "rspec", ">= 2.11.0"
+  # gem "rspec-rails", ">= 2.11.0"
+  # gem "capybara", "~> 1.1.2"
+  # gem "combustion", "~> 0.3.2"
+end

data/Gemfile.lock

@@ -0,0 +1,105 @@
+GEM
+  remote: http://rubygems.org/
+  specs:
+    actionmailer (3.2.13)
+      actionpack (= 3.2.13)
+      mail (~> 2.5.3)
+    actionpack (3.2.13)
+      activemodel (= 3.2.13)
+      activesupport (= 3.2.13)
+      builder (~> 3.0.0)
+      erubis (~> 2.7.0)
+      journey (~> 1.0.4)
+      rack (~> 1.4.5)
+      rack-cache (~> 1.2)
+      rack-test (~> 0.6.1)
+      sprockets (~> 2.2.1)
+    activemodel (3.2.13)
+      activesupport (= 3.2.13)
+      builder (~> 3.0.0)
+    activerecord (3.2.13)
+      activemodel (= 3.2.13)
+      activesupport (= 3.2.13)
+      arel (~> 3.0.2)
+      tzinfo (~> 0.3.29)
+    activeresource (3.2.13)
+      activemodel (= 3.2.13)
+      activesupport (= 3.2.13)
+    activesupport (3.2.13)
+      i18n (= 0.6.1)
+      multi_json (~> 1.0)
+    arel (3.0.2)
+    builder (3.0.4)
+    diff-lcs (1.1.3)
+    erubis (2.7.0)
+    git (1.2.5)
+    hike (1.2.2)
+    i18n (0.6.1)
+    jeweler (1.8.4)
+      bundler (~> 1.0)
+      git (>= 1.2.5)
+      rake
+      rdoc
+    journey (1.0.4)
+    json (1.7.5)
+    mail (2.5.3)
+      i18n (>= 0.4.0)
+      mime-types (~> 1.16)
+      treetop (~> 1.4.8)
+    mime-types (1.23)
+    multi_json (1.7.2)
+    polyglot (0.3.3)
+    rack (1.4.5)
+    rack-cache (1.2)
+      rack (>= 0.4)
+    rack-ssl (1.3.3)
+      rack
+    rack-test (0.6.2)
+      rack (>= 1.0)
+    rails (3.2.13)
+      actionmailer (= 3.2.13)
+      actionpack (= 3.2.13)
+      activerecord (= 3.2.13)
+      activeresource (= 3.2.13)
+      activesupport (= 3.2.13)
+      bundler (~> 1.0)
+      railties (= 3.2.13)
+    railties (3.2.13)
+      actionpack (= 3.2.13)
+      activesupport (= 3.2.13)
+      rack-ssl (~> 1.3.2)
+      rake (>= 0.8.7)
+      rdoc (~> 3.4)
+      thor (>= 0.14.6, < 2.0)
+    rake (10.0.4)
+    rdoc (3.12)
+      json (~> 1.4)
+    rspec (2.11.0)
+      rspec-core (~> 2.11.0)
+      rspec-expectations (~> 2.11.0)
+      rspec-mocks (~> 2.11.0)
+    rspec-core (2.11.1)
+    rspec-expectations (2.11.3)
+      diff-lcs (~> 1.1.3)
+    rspec-mocks (2.11.2)
+    sprockets (2.2.2)
+      hike (~> 1.2)
+      multi_json (~> 1.0)
+      rack (~> 1.0)
+      tilt (~> 1.1, != 1.3.0)
+    thor (0.18.1)
+    tilt (1.3.7)
+    treetop (1.4.12)
+      polyglot
+      polyglot (>= 0.3.1)
+    tzinfo (0.3.37)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (>= 1.1)
+  jeweler (~> 1.8.4)
+  rails (>= 3.2.0)
+  rdoc (~> 3.12)
+  rspec (>= 2.11.0)

data/LICENSE

@@ -1,5 +1,5 @@
 
-Copyright (C) 2011 by Awexome Labs, LLC
+Copyright (C) 2012 by Awexome Labs, LLC
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

data/README.rdoc

@@ -1,116 +1,186 @@
 = DoesFacebook
 
-The Awexome Labs rails plugin for handling Facebook application credentials and authentication. 
-Also provides helpers and convenience methods for canvas applications.
+Lightweight gem enables your Rails application to quickly and simply integrate with Facebook,
+while also providing configuration and convenience methods for Facebook app developers.
 
-You may also be interested in accessing content on Facebooks Open Graph API. For that, consider
-this gem's brother from the same mother, DoesOpenGraph[https://github.com/awexome/doesopengraph].
+== Install
 
+DoesFacebook is designed to work with Rails applications. To get started, add +doesfacebook+
+to your +Gemfile+:
 
-== Installation
+  gem "doesfacebook"
 
-To install the gem, do the usual:
+DoesFacebook is built against Rails versions 3.2 and higher, which it requires at runtime. In
+development, the additional gem requirements include bundler, jeweler, and rspec.
 
-  gem install doesfacebook
-  
-If you plan on using DoesFacebook in a project with a Gemfile:
+== Configure
 
-  gem "doesfacebook"
-  
-You can live on the edge, too:
+To work with the Facebook API and handle Canvas application requests, you must specify
+configuration details for the Facebook applications that your Rails application will support
+in an initializer file. This file allows you to use a simple DSL to define each application.
 
-  gem "doesfacebook", :git=>"git://github.com/awexome/doesfacebook.git"
+To get started, you can generate a boilerplate initializer in your directory by running the
+included generator:
 
+  rails generate does_facebook:config
 
-== Configuration
+This generates a file +doesfacebook.rb+ in your +config/initializers+ directory containing a
+sample app definition and a commented section containing optional selector behavior.
 
-You can configure your Facebook applications for use in your Rails project by specifying them
-within the "doesfacebook.yml" file under config/
+=== Facebook Applications
 
-To generate a boilerplate configuration file, run the generator:
+DoesFacebook supports any number of Facebook applications within a single Rails application.
+Facebook applications are created and defined within the
+{Facebook Developers Dashboard}[https://developers.facebook.com/].
+
+You can customize the configuration for any number of supported applications in the initializer
+file. A typical case is to have a Facebook application for each environment in which your Rails
+application will run (development, staging, production, etc.), but you are not tied to this
+convention and can define any number of Facebook applications your Rails application will support.
+
+A sample Facebook application definition:
+
+  # Support a Facebook application with my Rails app:
+  config.add_application(
+    id: 123456789012345,                                  # <= "App ID" in FB dashboard
+    secret: "abcdefghijklmnopqrstuvwxyzABCDEF"            # <= "App Secret" in FB dashboard
+    namespace: "your_app_namespace",                      # <= "Namespace" in FB dashboard
+    canvas_url: "http://your.dev.server.com/and/path",    # <= Under "App on Facebook"
+    secure_canvas_url: "https://secure.dev.server"        # <= Under "App on Facebook"
+  )
+
+The example above shows a declaration with the required keys defined. App ID, Secret, Namespace,
+and the callback URLs are used to handle incoming requests from Facebook, parse and validate
+POST parameters from Facebook, and more.
+
+Add additional applications by adding subsequent +config.add_application+ calls to your
+initializer.
+
+You can define, for your reference and remote configuration purposes, any configuration key for
+your application specified in the documentation on developers.facebook.com.
 
-  rails generate does_facebook:config
-  
-The appropriate application configuration will be loaded for each request based on the callback
-path of your application. The host of each incoming request will be compared against the callback_url
-or ssl_callback_url fields of your app. A sample configuration looks like this:
 
-  my_sweet_facebook_app:
-    app_id: 1234567890
-    secret_key: a1b2c3d4e5f6g7h8i9j0k1l
-    namespace: my_sweet_canvas_name
-    callback_url: http://your.server.com/and/path
-    ssl_callback_url: https://your.secure.server.com/and/path
+=== Matching Apps with Requests
 
-Top-level keys in this file are configuration names. This allows you to specify many different apps
-which can be used within any environment, provided they have different callback patterns.
+By default, the +canvas_url+ and +secure_canvas_url+ keys of your configured applications will be
+compared against incoming requests to match each request with a single Facebook application.
 
-If you do have one app for each environment, however, naming an app after the corresponding Rails
-environment ("development","production",etc.) will provide a fallback should the request host not
-directly resolve to a callback_url
+For example, if a request comes from the Facebook canvas to "http://dev1.com/abe" and strikes your
+application, DoesFacebook will match this request with the Facebook application containing a +canvas_url+
+that is a part of the request URL "http://dev1.com/abe". If the request comes in over SSL/HTTPS,
+DoesFacebook will compare against the +secure_canvas_url+ key of your applications.
 
-The typical configuration options are as follows:
+As a +Proc+, this default selection method is defined like so:
 
-* app_id: Facebook ID of your application
-* secret_key: Facebook secret key of your application (used to parse and validate Facebook requests)
-* namespace: The "myapp" from "http://apps.facebook.com/myapp" used frequently for link generation and redirection (previously, this configuration field was known as "canvas_name", but Facebook has deprecated that name in favor of "namespace")
-* callback_url: The server callback URL for your app. Used to identify the proper configuration which should be loaded for each request.
-* ssl_callback_url: The server callback for secure, HTTPS requests. Required for production apps. Can be different from your non-secure callback_url
+  app_selector = Proc.new() do |request, apps|
+    apps.find do |a|
+      callback_path = request.ssl? && a.supports_ssl? ? a.secure_canvas_url : a.canvas_url
+      request.url.match(/^#{callback_path}.*/)
+    end
+  end
 
-These parameters relate to settings in the Facebook Developers application configuration panel,
-which you can review at https://developers.facebook.com/apps and should be easy to copy and paste
-in as you need for each application.
+You can, however, override this selector logic. In the +configure+ block within your initializer
+file, you can make a call to the +app_selector+ method to override this logic with a custom +Proc+
+operating on the request and list of defined applications. Here's an example call:
+
+  # Select the active Facebook application based on subdomain:
+  config.app_selector = Proc.new() do |request, apps|
+    apps.find do |a|
+      request.domains.last.match(/_dev$/) ? a.namespace.match(/_dev$/) : a.namespace.match(/_pro$/)
+    end
+  end
+
+You can change this, too, to seek in your database for an app definition, or elsewhere. You are not
+limited to solely the list of defined applications.
 
 
 == Usage
 
-To parse and validate requests from Facebook, simply add the following declaration to your controller:
+To use DoesFacebook in a given controller in your application, you simply add the following
+invocation to your controller:
 
   does_facebook
 
-Now, with each incoming request, DoesFacebook will parse the "signed_request" parameter against your
-application's keys, as described at http://developers.facebook.com/docs/authentication/signed_request
+Now, with each incoming request to this controller, DoesFacebook will add the following
+functionality:
+
+* Convert POST requests from (apps.)facebook.com into GET requests to preserve RESTfulness in your app
+* Select the proper Facebook application from your configuration
+* Validate the +signed_request+ parameter Facebook sends to your application to ensure the request is from Facebook
+* Parse the contents of the +signed_request+ (user, brand page, user auth token, etc.) and make them available to your controller as +fb_params+
+* Provide controller extensions which give you access to Facebook shortcuts in your controller
+* Include helpers in your views that allow you quick access to configuration
+
+=== Controller Extensions
+
+Within your controller, you can now access +fb_app+ and +fb_params+ to view the configuration of the
+currently active application and the parameters passed by Facebook as part of the +signed_request+. These
+are available in your regular controller actions and before filters.
+
+Also, you will gain convenience methods +url_for_canvas+ and +redirect_to_canvas+, which behave just like
+their non-canvas Rails equivalents, but ensure that the URL given or redirection provided includes the
+properly-formatted "http(s)://apps.facebook.com/namespace" convention and take place in the top browser frame.
+These are useful for any end-user activity that requires typical redirects or URL generation.
+
+=== View Helpers
+
+Within your views, you will now have access to a wealth of helpers that provide shortcuts to configuration
+and other Facebook features:
+
+* +fb_app+ - Full configuration of the active Facebook application in use
+* +app_id+ - The active application's "App ID", required by some FB JavaScript methods
+* +app_namespace+ - The active application's "namespace" configuration value.
+* +app_canvas_url+ - The full URL to the active application's canvas (e.g., http://apps.facebook.com/myapp)
+
+You also receive a few beneficial link methods:
 
-This allows your application to verify and properly handle requests from Facebook, as well as view any
-additional data and parameters your app is sent by Facebook, such as the current user ID, active
-Facebook page, and more.
+* +url_for_canvas+ - Like the standard +url_for+, but ensures the endpoint is in the Facebook canvas
+* +link_to_canvas+ - Use as you would the regular +link_to+ helper; generates links to the canvas and properly targets the link to "_top" frame to keep app within canvas and not break into your iframe
 
-By default, to enhance your iframe development, the "signed_request" parameter from Facebook will be
-stuffed into the session and subsequent requests that lack a "signed_request" parameter (links from
-your internal iframe clicks, perhaps), will used this signed_request. This allows you to build a canvas
-or page tab application like any other web application and not worry about passing around the signed_request
-parameter yourself.
+Quick Facebook helpers for representing users and bootstrapping your application's JS SDK implementation
+are also provided:
 
-  does_facebook :session=>false     # <== Use this invocation to prevent session stuffing
+* +profile_pic+ - Builds out an image tag containing the profile picture of the specified user. Pass +type+ and basic +image_tag+ options along in the +opts+ hash to customize.
+* +fb_init+ - Bootstrap an FB JS SDK implementation with this call, which will automatically inject the JS SDK with proper values for +appId+ as well as the proper browser-compatibility +channelUrl+ file.
 
-Within your controllers which declare _does_facebook_ (or inherit from a controller which does), you
-will now have access to the following niceties:
+Display a profile photo of a user with Facebook ID 1234567890 in a view with some view customizations:
 
-* redirect_to_canvas: Generate a JS top frame redirection which keeps users inside your application's canvas as opposed to loading links only within your app's iframe
-* @fbparams: This hash will be set with all keys and values Facebook provided to you for this request (things like user id, page id, logged in status, region, locale, etc.)
+  <%= profile_pic 1234567890, :type=>"small", :style=>"border: 2px solid blue;" %>
 
-Within your views, you have access to a wealth of helpers that will make many aspects of developing
-against the Facebook platform easier:
+Complete a basic invocation of +fb_init+ from your layout:
 
-* app_id: The current application's id, parsed from doesfacebook.yml
-* app_callback_url: The current application's callback URL, parsed from doesfacebook.yml
-* app_namespace: The current application's canvas shortname, parsed from doesfacebook.yml (aliased as "app_canvas_name" for backwards compatibility)
-* app_canvas_url: The full URL to the application canvas (e.g., http://apps.facebook.com/myapp)
-* url_for_canvas(url_opts={}): Like the standard url_for, but ensures the endpoint is in the Facebook canvas
-* link_to_canvas(text, url_opts={}, html_opts={}): Use as you would the regular link_to helper; generates links to the canvas and properly targets the link to "_top" frame to keep app within canvas and not break into your iframe
+  <%= fb_init() %>
 
-Other helpers and useful shortcuts being added regularly.
+And you will, in effect, be generating this properly-formed JS SDK boot in your layout:
 
+  <!-- Facebook JS SDK -->
+  <div id="fb-root"></div>
+  <script>
+    window.fbAsyncInit = function() {
+      FB.init({"appId":123456789012345,"channelUrl":"/channel.html","status":true,"cookie":true,"xfbml":false});
+    };
+    (function(d){
+       var js, id = 'facebook-jssdk', ref = d.getElementsByTagName('script')[0];
+       if (d.getElementById(id)) {return;}
+       js = d.createElement('script'); js.id = id; js.async = true;
+       js.src = "//connect.facebook.net/en_US/all.js";
+       ref.parentNode.insertBefore(js, ref);
+     }(document));
+  </script>
 
-Now, you are armed with the tools you need to build an app within the Facebook platform simply and quickly.
+You can override any of the standard options to +FB.init+ by passing values for the keys you wish to change
+in the +opts+ hash to +fb_init+.
 
+If you pass a block to +fb_init+, you can include additional JavaScript within the +window.fbAsyncInit+ function.
+This can be useful to attach Facebook listeners or handlers to events such as +edge.create+ or similar. You can
+learn the nitty-gritty details of JS SDK initialization at https://developers.facebook.com/docs/reference/javascript/
 
 
 
 
 == Copyright
 
-Copyright 2011-12 Awexome Labs, LLC 
+Copyright 2011-12 Awexome Labs, LLC
 http://awexomelabs.com
 http://facebook.com/AwexomeLabs
 http://twitter.com/awexomelabs

data/ROADMAP.rdoc

@@ -0,0 +1,55 @@
+= DoesFacebook Road Map
+
+The previous trunk of DoesFacebook (v0.*) has been closed to make way for
+cleaner implementation and new features in the upcoming v1.* branch. Within
+code, these tracks are represented by the
+{"v0" (original) branch}[https://github.com/awexome/doesfacebook/tree/v0]
+and the 
+{"v1" (new) branch}[https://github.com/awexome/doesfacebook/tree/v1].
+
+At this time, v1 is merging into master.
+
+This document reflects the planned changes for versions going forward.
+
+
+== v1.0.0
+
+The v1 branch is the current branch of development.
+
+Expected release by November 2012. Changes API and methods of configuration
+while adding deeper integrations, new features, and currently unsupported
+Facebook features. Will break some aspects of code written against prior
+versions of the library.
+
+Planned features:
+
+* Remove support for previously-deprecated methods
+* Change format of configuration, following config/initializers pattern
+* Allow app configurations to be loaded via YAML, Proc, database
+* Bring proper url_for_canvas support into controllers
+* Increase flexibility of JS-based redirect with custom partial, template, message, and/or delay loaded from configuration or directly in method call
+* Change standards and optimizations for helpers, filters
+* Provide user, page, and referrer details to apps in filters
+* Add deeper integration options with Graph API via DoesOpenGraph
+
+
+== v0.6.0
+
+Maintained in the v0 branch, this is the prior path of development.
+
+Released October 11, 2012. Fixes issues and extends functionality of
+the existing v0.5.* track. Introduces deprecations, but does not break
+functionality.
+
+Implemented features:
+
+* Add proper deprecation messaging for deprecated configurations and methods
+
+
+== Support
+
+Support for v0 branch releases will continue alongside v1 branch releases
+following the release of v1.0.0, however only bugfixes and tweaks will
+be added to the v0 branch once v1.0.0 is released. All new feature
+development and required alterations for Facebook-initiated changes 
+will take place in the v1 branch only.

data/Rakefile

@@ -0,0 +1,64 @@
+# encoding: utf-8
+
+require "rubygems"
+require "bundler"
+begin
+  Bundler.setup(:default, :development)
+rescue Bundler::BundlerError => e
+  $stderr.puts e.message
+  $stderr.puts "Run `bundle install` to install missing gems"
+  exit e.status_code
+end
+require "rake"
+
+require "jeweler"
+Jeweler::Tasks.new do |gem|
+  # gem is a Gem::Specification... see http://docs.rubygems.org/read/chapter/20 for more options
+  gem.name = "doesfacebook"
+  gem.homepage = "http://github.com/awexome/doesfacebook"
+  gem.license = "MIT"
+  gem.summary = %Q{Lightweight gem enables your Rails application to quickly and simply integrate with Facebook}
+  gem.description = %Q{Lightweight gem enables your Rails application to quickly and simply integrate with Facebook}
+  gem.email = "engineering@awexomelabs.com"
+  gem.authors = ["Awexome Labs"]
+  # dependencies defined in Gemfile
+end
+Jeweler::RubygemsDotOrgTasks.new
+
+require "rspec/core"
+require "rspec/core/rake_task"
+RSpec::Core::RakeTask.new(:spec) do |spec|
+end
+
+RSpec::Core::RakeTask.new(:rcov) do |spec|
+  spec.rcov = true
+end
+
+task :default => :spec
+
+# require "rake/testtask"
+# Rake::TestTask.new(:test) do |test|
+#   test.libs << "lib" << "test"
+#   test.pattern = "test/**/test_*.rb"
+#   test.verbose = true
+# end
+
+# require "rcov/rcovtask"
+# Rcov::RcovTask.new do |test|
+#   test.libs << "test"
+#   test.pattern = "test/**/test_*.rb"
+#   test.verbose = true
+#   test.rcov_opts << "--exclude "gems/*""
+# end
+
+# task :default => :test
+
+require "rdoc/task"
+Rake::RDocTask.new do |rdoc|
+  version = File.exist?("VERSION") ? File.read("VERSION") : ""
+
+  rdoc.rdoc_dir = "rdoc"
+  rdoc.title = "DoesKeyValue #{version}"
+  rdoc.rdoc_files.include("README*")
+  rdoc.rdoc_files.include("lib/**/*.rb")
+end

data/VERSION

@@ -0,0 +1 @@
+1.0.0.pre1

data/doesfacebook.gemspec

@@ -0,0 +1,71 @@
+# Generated by jeweler
+# DO NOT EDIT THIS FILE DIRECTLY
+# Instead, edit Jeweler::Tasks in Rakefile, and run 'rake gemspec'
+# -*- encoding: utf-8 -*-
+
+Gem::Specification.new do |s|
+  s.name = "doesfacebook"
+  s.version = "1.0.0.pre1"
+
+  s.required_rubygems_version = Gem::Requirement.new("> 1.3.1") if s.respond_to? :required_rubygems_version=
+  s.authors = ["Awexome Labs"]
+  s.date = "2013-05-21"
+  s.description = "Lightweight gem enables your Rails application to quickly and simply integrate with Facebook"
+  s.email = "engineering@awexomelabs.com"
+  s.extra_rdoc_files = [
+    "LICENSE",
+    "README.rdoc"
+  ]
+  s.files = [
+    "CHANGELOG.rdoc",
+    "Gemfile",
+    "Gemfile.lock",
+    "LICENSE",
+    "README.rdoc",
+    "ROADMAP.rdoc",
+    "Rakefile",
+    "VERSION",
+    "doesfacebook.gemspec",
+    "lib/doesfacebook.rb",
+    "lib/doesfacebook/application.rb",
+    "lib/doesfacebook/configuration.rb",
+    "lib/doesfacebook/controller_extensions.rb",
+    "lib/doesfacebook/error.rb",
+    "lib/doesfacebook/middleware.rb",
+    "lib/doesfacebook/session.rb",
+    "lib/generators/doesfacebook/config/config_generator.rb",
+    "lib/generators/doesfacebook/config/templates/doesfacebook.rb",
+    "lib/helpers/does_facebook_helper.rb",
+    "public/channel.html"
+  ]
+  s.homepage = "http://github.com/awexome/doesfacebook"
+  s.licenses = ["MIT"]
+  s.require_paths = ["lib"]
+  s.rubygems_version = "1.8.24"
+  s.summary = "Lightweight gem enables your Rails application to quickly and simply integrate with Facebook"
+
+  if s.respond_to? :specification_version then
+    s.specification_version = 3
+
+    if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then
+      s.add_runtime_dependency(%q<rails>, [">= 3.2.0"])
+      s.add_development_dependency(%q<bundler>, [">= 1.1"])
+      s.add_development_dependency(%q<jeweler>, ["~> 1.8.4"])
+      s.add_development_dependency(%q<rdoc>, ["~> 3.12"])
+      s.add_development_dependency(%q<rspec>, [">= 2.11.0"])
+    else
+      s.add_dependency(%q<rails>, [">= 3.2.0"])
+      s.add_dependency(%q<bundler>, [">= 1.1"])
+      s.add_dependency(%q<jeweler>, ["~> 1.8.4"])
+      s.add_dependency(%q<rdoc>, ["~> 3.12"])
+      s.add_dependency(%q<rspec>, [">= 2.11.0"])
+    end
+  else
+    s.add_dependency(%q<rails>, [">= 3.2.0"])
+    s.add_dependency(%q<bundler>, [">= 1.1"])
+    s.add_dependency(%q<jeweler>, ["~> 1.8.4"])
+    s.add_dependency(%q<rdoc>, ["~> 3.12"])
+    s.add_dependency(%q<rspec>, [">= 2.11.0"])
+  end
+end
+