Typically you'd use a library like https://github.com/nateware/redis-objects. As its README says, it's not just another way to store ActiveRecords, since you may as well keep it simple and use MySQL or Postgres if all you want is ActiveRecords. Instead, redis-object will let you use Redis data structures as they are intended to be used.
This is not an ORM. People that are wrapping ORM’s around Redis are missing the point.
The killer feature of Redis is that it allows you to perform atomic operations on individual data structures, like counters, lists, and sets. The atomic part is HUGE. Using an ORM wrapper that retrieves a "record", updates values, then sends those values back, removes the atomicity, cutting the nuts off the major advantage of Redis. Just use MySQL, k?
You can also just install the Redis gem and make your own calls to Redis, but that kind of low-level programming would largely defeat the purpose of using a powerful framework like Rails.