It doesn't seem to be working in Rails 4 due to version dependencies I guess. Any updates on the way?
If the API hasn't changed too much, this should be easy. However, I haven't investigated compatibility, and there's nothing currently on the radar. We'd of course welcome a pull request that adds support.
Well. I just upped the dependency versions for active_support and action_pack locally and It works. But I'm not sure that it's legitimate and reliable way, so I would aware of making a pull request with these changes.
@youroff I haven't investigated yet, but I've seen most of the methods to accept an optional argument options. https://github.com/rails/rails/blob/master/activesupport/lib/active_support/cache.rb#L274
Which kinda sucks because it creates an infinite protocol.
Isn't it the same in current stable release? Anyway, I use it only as a session storage. Do you think it's ok?
Yeah, just noticed. I upgrated tests to Rails 3.2.x and they're passing. Another reason why having that option = nil everywhere sucks.
option = nil
For what it's worth, I have been using redis-store with rails 4 successfully for a while now, with no modifications to the actual source. Granted, I'm only using it in very basic ways (pretty much just the cache helper).
Here's what I did:
I forked this repo, and bumped up the the gem dependencies in a few of the gemspecs:
'actionpack', '>= 3.2.3'
'activesupport', '>= 3.2.3'
'rack', '~> 1.5.2'
The two commits are 7995257 and 99aa42f .
And then, in my Gemfile, I just need to use those forks:
gem 'redis-store', github: "bricker/redis-store"
gem 'redis-actionpack', github: "bricker/redis-store"
gem 'redis-activesupport', github: "bricker/redis-store"
gem 'redis-rack', github: "bricker/redis-store"
Anybody is welcome to use my forks, of course, but I have no intention of maintaining or updating these at all - this is a temporary workaround so that I could get Redis working with Rails 4 beta.
Thx @bricker, I've cleaned up the great work everyone has done on these projects to create an updated set of gems for Rails 4. Specifically, I'm using them to serialize Rails 4 sessions into Redis as JSON.
What's the status on this? 507935e incorporates the change to require 'activesupport in >= 3.2.3'. Simply using master should work just fine (I gave it a shot, no problems so far).
@jodosha any issues that prevents you from making a release?
@tisba @nathantsoi I'm looking for help for close these tickets, and release the gems. Do you wanna contribute?
happy to help, not sure what the question is though? as @tisba said, seems like 507935e takes care of the compatibility issue?
what @nathantsoi said, not sure what to do about this issue otherwise…
@tisba @nathantsoi that commit only enables Travis CI build to be run against Rails 4, but the production code isn't there yet.
what's the status of this.
I get "FiberError - can't yield from root fiber:" with Ruby 2.0
It's working for me now, as Rails 4 support has been released. Fiber error was caused by websocket-rails.
Released a few days ago. http://rubygems.org/gems/redis-rails