NOTE: If you were contributing to the 0.70.x version of this extension, please make sure you are using the 0_70_stable branch, as this branch has recently been forced push to in order to release the 1.0.x extension rewrite.
Core for all Social media related functionality for Spree. The Spree Social gem handles authorization, account creation and association through social media sources such as, Twitter and Facebook. This requires the edge source of Spree. This gem is beta at best and should be treated as such. Features and code base will change rapidly as this is under active development. Use with caution.
Add this to your gem file Gemfile
gem "spree_social", :git => "git://github.com/spree/spree_social.git"
bundle update
bundle exec rake spree_social:install
rake db:migrate
Login as an admin user and navigate to Configuration > Social Authentication Methods
Click on the New Authentication Method button to enter the key obtained from their respective source (See below for instructions on setting up the various providers)
Multiple key entries can now be entered based on the rails environment. This allows for portability and the lack of need to check in your key to your repository. You also have the ability to enable and disable sources. These setting will be reflected on the client UI as well.
Please note that you will still need to restart you server after entering you keys. This is required otherwise Devise and OmniAuth will not have the key pair available to them for use. Also if you are running Spree with SSL, make sure you setup you applications at the social network of you choice EXACTLY as it in seen in the browser, OAuth will fail if it experiences a local redirect through the various handshakes (e.g. if you have https://www.example.com as your domain for SSL, that is the URL that need to be uses as the domain at the OAuth source of your choice).
OAuth Applications @ Facebook, Twitter and / or Github are supported out of the box but you will need to setup applications are each respective site as follows for public use and for development.
All URLs must be in the form of domain.tld you may add a port as well for development
Facebook: http://www.facebook.com/developers/createapp.php
- Name the app what you will and agree to the terms.
- Fill out the capcha
- Under the Web Site tab
- Site URL: http://your_computer.local:3000 for development / http://your-site.com for production
- Site domain: your-computer.local / your-site.com respectively
Twitter: http://dev.twitter.com/apps/new
- Name and Description must be filled in with something
- Application Website: http://your_computer.local:3000 for development / http://your-site.com for production
- Application Type: Browser
- Callback URL: http://your_computer.local:3000 for development / http://your-site.com for production
- Default Access Type: Read & Write
- Save Application
Github: http://github.com/account/applications/new
- Name The Application
- Main URL: http://your_computer.local:3000 for development / http://your-site.com for production
- Callback URL: http://your_computer.local:3000 for development / http://your-site.com for production
- Click Create
This does not seem to be a listed Github item right now. To View and / or edit your applications goto http://github.com/account/applications/
- Google (OAuth)
git clone git://github.com/railsdog/spree
cd spree
rake sandbox
git clone git://github.com/spree/spree_social
add this to sandbox/Gemfile
gem "spree_social", :path => "../spree_social"
bundle update
rails g spree_social:install
bundle exec rake db:migrate
rake test_app inside of cloned spree_social folder
rspec spec
Most auth sources supported by the Omniauth gem can be added. I attempt to keep the popular ones included and tested.
Copyright (c) 2012 John Brien Dilts, released under the New BSD License