Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/charlotte-ruby/devise_omniauth_engine

THIS REPO IS NOT ACTIVELY MAINTAINED AND PROBABLY NOT COMPATIBLE WITH LATEST DEVISE/OMNIAUTH
https://github.com/charlotte-ruby/devise_omniauth_engine

Last synced: about 2 months ago
JSON representation

THIS REPO IS NOT ACTIVELY MAINTAINED AND PROBABLY NOT COMPATIBLE WITH LATEST DEVISE/OMNIAUTH

Host: GitHub
URL: https://github.com/charlotte-ruby/devise_omniauth_engine
Owner: charlotte-ruby
License: mit
Created: 2011-05-11T16:25:01.000Z (over 13 years ago)
Default Branch: master
Last Pushed: 2012-08-18T13:47:44.000Z (over 12 years ago)
Last Synced: 2024-05-01T09:49:31.958Z (8 months ago)
Language: Ruby
Homepage:
Size: 199 KB
Stars: 6
Watchers: 2
Forks: 1
Open Issues: 0
Metadata Files:
- Readme: README.md
- License: LICENSE.txt

Awesome Lists containing this project

README

# devise_omniauth_engine

# THIS WAS A PROOF OF CONCEPT AND HAS NOT BEEN UPDATED IN A LONG TIME. I WOULD RECOMMEND NOT USING IT FOR NEW PROJECTS.

This is meant for blank Rails 3 apps as an automated setup for Devise & Omniauth. This engine will install devise and omniauth into your app and provide you with a callback controller that handles Twitter, Facebook, Google and Yahoo. When you run the generator it performs the following steps for you:

1. rails generate devise:install
2. rails generate User
3. rails generate devise:views
4. Adds :omniauthable to the user model
5. Creates an Authentication model with provider, uid, and user_id. For example, Bob authenticates using twitter, it would add Bob's user_id, provider=twitter, and uid=uid provided by twitter
6. Adds "has_many :authentications" to User model
7. Overwrites the default Devise view in app/views/devise/shared/links, so it includes Google, Yahoo, Facebook & Twitter
8. Creates UsersController and index view. This is used as the default action after authentication.
9. Provides a YAML config file where you can enter your Twitter and Facebook API key/secret that will be used by Omniauth. Directory = config/yettings/devise_omniauth_engine.yml

## Install

Add it to your Gemfile (This will include devise and omniauth gems, so no need to add them)

gem "devise_omniauth_engine", :git=>"[email protected]:charlotte-ruby/devise_omniauth_engine.git"

Install it using Bundler

bundle install

Run the generator

rails g devise_omniauth_engine:install

There are a few things that the devise generators will tell you to do regarding flash, mailer, and your root route. You will need to do these manually after the generator finishes.

Run migrations (devise and authentications model)

rake db:migrate

By default, dev and test have working app keys for twitter and facebook apps. These are just test apps, so you will want to add your own app keys/secrets to the config file - config/yettings/devise_omniauth_engine.yml

defaults: &defaults
twitter_key:
twitter_secret:
facebook_key:
facebook_secret:

After that you can customize the views. You can add buttons for Twitter, etc in this view:

app/views/devise/shared/_links.html.erb

NOTE: If you are using Webrick as your development or test server, it will not be able to handle the size of the packets sent back by Yahoo and Google. You should use mongrel instead:

#Gemfile
gem "mongrel", "1.2.0.pre2"

Install w/ bundler

bundle install

Start up your mongrel in dev

rails s

## TODO
1. Allow users to associate multiple external providers to one account. You are restricted to one per account currently.
2. Add all omniauth providers to the Devise.setup block. Callbacks controller method_missing may need to be updated to accommodate some of these

## Contributing to devise_omniauth_engine

* Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
* Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
* Fork the project
* Start a feature/bugfix branch
* Commit and push until you are happy with your contribution
* Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
* NOTE: YOU WILL NEED TO UPDATE THE USERNAMES/PASSWORDS FOR THE AUTH FEATURE WITH YOUR OWN CREDENTIALS OR IT WILL FAIL
* Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.