Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to Rails4 and Ruby 2.0.0 #51

Closed
wants to merge 2 commits into from

Conversation

jimnanney
Copy link
Contributor

Update to rails 4 and ruby 2.0.0. Change Sprockets to Sprockets Rails, remove assets group, fix deprecation warnings and add uhf gem to silence the fog warnings.

@@ -4,7 +4,7 @@
require "active_record/railtie"
require "action_controller/railtie"
require "action_mailer/railtie"
require "active_resource/railtie"
#require "active_resource/railtie"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just remove these unused requires?

@bf4
Copy link
Member

bf4 commented Oct 31, 2013

Awesome!

@jimnanney
Copy link
Contributor Author

I'll make those changes and push them up into this PR. :)

@jimnanney
Copy link
Contributor Author

Updated to include the commented changes. I'm adapting ruby friends to work for #RubyOnSails and while I was there decided it could use an upgrade to rails 4

@bf4
Copy link
Member

bf4 commented Oct 31, 2013

@jimnanney funny, I have my own fork/instance for general conference tweets, which is how I got into it :)

@jimnanney
Copy link
Contributor Author

Heh, I wanted a quick twitter aggregator, and ruby friends seemed perfect. If it were an engine would probably be even better!

Anything else I might need to change on this pull request?

@bf4
Copy link
Member

bf4 commented Oct 31, 2013

Yeah, we never finished this, did we ;( https://github.com/bf4/rubyfriends/tree/tweet-engine

@bf4
Copy link
Member

bf4 commented Oct 31, 2013

Let me know if you need any help getting it set up. Note, also, that it doesn't actually cache anything.

@jimnanney
Copy link
Contributor Author

Exactly! We should, but gonna have to be after Ruby On Sails and after
RubyConf.

On Wed, Oct 30, 2013 at 9:12 PM, Benjamin Fleischer <
[email protected]> wrote:

Yeah, we never finished this, did we ;(
https://github.com/bf4/rubyfriends/tree/tweet-engine


Reply to this email directly or view it on GitHubhttps://github.com//pull/51#issuecomment-27456346
.

@bf4
Copy link
Member

bf4 commented Oct 31, 2013

Did the cucumber tests pass for you? RSpec did, but got a unexpected token at '' (Twitter::Error::DecodeError) on cucumber

@bf4
Copy link
Member

bf4 commented Oct 31, 2013

Ah, removed the old cassette, and saw we need to update cucumber cucumber/cucumber-rails#253

@bf4
Copy link
Member

bf4 commented Oct 31, 2013

@jimnanney
Copy link
Contributor Author

added cucumber from the github repo, due to that bug. thanks for tracking it down, I completely forgot to run duke tests.

@bf4
Copy link
Member

bf4 commented Oct 31, 2013

em.. went ahead and just used a local commit since it wasn't really relevant to your changes

@bf4
Copy link
Member

bf4 commented Oct 31, 2013

Deploying it now :) (Also tested on my own instance)

@bf4 bf4 closed this Oct 31, 2013
@bf4 bf4 reopened this Oct 31, 2013
@bf4
Copy link
Member

bf4 commented Oct 31, 2013

Stupid github. I wanted it to give you credit for the merge, but it didn't pick it up for some reason.

@bf4
Copy link
Member

bf4 commented Oct 31, 2013

Hmm.. assets didn't compile properly for the rubyfriends app... but did on my other heroku app... http://rubyfriends.com/ http://rubyfriends.herokuapp.com/

@jimnanney
Copy link
Contributor Author

The commits got credited to me. No worries

@jimnanney
Copy link
Contributor Author

The assets are part of the application.rb bundler setup, I'll send another pull request

@jimnanney jimnanney closed this Oct 31, 2013
@bf4
Copy link
Member

bf4 commented Oct 31, 2013

Or re-add to this one... I'll re-merge it

@jimnanney
Copy link
Contributor Author

too late, already set in 2nd pull request

@jimnanney
Copy link
Contributor Author

After more testing, I think you need the default scope, otherwise they are published in reverse order on the ruby friends page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants