I have installed this branch and added the recommended initialization code in initializers/omniauth.rb.
However, if I examine configratron, there is no entry for omniauth. Any thoughts on what I might be missing. Also, I'm not sure where the additional login buttons should show up once I get it recognizing omniauth. Thanks On Feb 22, 11:29 am, Bruno Bornsztein <[email protected]> wrote: > Just a quick update; Rails3 development continues, and I've got a new branch > open using OmniAuth for social login (Facebook, Twitter, etc.). See here: > > https://github.com/bborn/communityengine/tree/omniauth/ > > <https://github.com/bborn/communityengine/tree/omniauth/>Justin: please feel > free to send a pull request. > > Thanks, > Bruno > > > > On Sun, Feb 20, 2011 at 5:03 PM, Justin G <[email protected]> wrote: > > Bruno, > > > I am very excited about the rails3 port. I was able to successfully > > run the tests also, but it took a bit of work for me to get my > > environment set up correctly. Here are some of the steps I took to > > get things working correctly. I hope this will help others that run > > into similar issues. > > > When running database migrations, I ran into some YAML errors. It > > appears that my system is using psych for reading in YAML files. > > Apparently, this is activated by default with RubyGems 1.5, but I'm > > still on RubyGems 1.3.7 so I'm not sure why it is being activated. I > > found that adding the following to my application.rb fixed my > > problems: > > > require ‘yaml’ > > YAML::ENGINE.yamler= ‘syck’ > > > I also found a few development dependencies needed to run the tests: > > jeweler and simplecov. The tests were also having trouble loading > > test_helper for me. I made the following change in many of the test > > cases: > > > -require File.dirname(__FILE__) + '/../test_helper' > > +require 'test_helper' > > > This also worked for me: require_relative '../test_helper' > > > I'll package this in a commit for you to pull if you agree with this > > change. > > > Also, I modified test_helper.rb to require simplecov directly, rather > > than as: require File.expand_path('../../../simplecov/lib/simplecov', > > __FILE__) > > > Finally, I needed a test database to run against. In order to create > > the test database, I ran RAILS_ENV="test" rake db:migrate from under > > test/testapp/ The Gemfile under this folder had more relative paths, > > and I ended up just emulating that expected folder structure on my > > system to get everything up and running. In the end, I was able to > > get 'rake test' to run with all tests passing! > > > I'm definitely not as familiar with testing as I should be. This is > > an area I know I will need to get better with as I eventually work to > > migrate my custom CE changes over to rails3. In other words I've made > > some quick and dirty modifications in the past without paying my > > testing taxes. So, please let me know if anything I've said above > > seems to indicate that I'm doing something completely wrong. > > > Thanks! > > Justin > > > On Feb 16, 2:28 pm, Bruno Bornsztein <[email protected]> > > wrote: > > > Hi everyone, > > > I'm happy to say the Rails3 branch test suite is now 100% passing. This > > is a > > > good start, but it doesn't mean CE is ready for Rails 3 in production; > > code > > > coverage still needs improving, and I haven't done much actual testing in > > > the browser, so I'm sure some things are still off. Also, there are a few > > > tweaks I still need to make (listed at the top of the CHANGELOG), and I > > > haven't done any work on creating an upgrade path for Rails 2.x CE apps. > > > > So, I need your help! Please try setting up a new Rails 3.1 app with the > > CE > > > gem (use the Rails3 branch in your Gemfile) and test things out. The more > > > people start playing around with this branch, the faster we'll get it to > > a > > > stable point so I can release it. > > > >https://github.com/bborn/communityengine/tree/rails3 > > > > Thanks! > > > Bruno > > > -- > > You received this message because you are subscribed to the Google Groups > > "CommunityEngine" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/communityengine?hl=en. -- You received this message because you are subscribed to the Google Groups "CommunityEngine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/communityengine?hl=en.
