Hooking up to Redis?

[MarkMurphy]

Would be nice to see an example in the REDME of how this can be configured to connect to Redis. Can someone provide me with a link which explains how to do that?

[zmillman]

By default, Rack::Attack will use whichever caching backend is configured as Rails.cache, although you can specify a different cache in your initializer:

From the example configuration:

  ### Configure Cache ###

  # If you don't want to use Rails.cache (Rack::Attack's default), then
  # configure it here.
  #
  # Note: The store is only used for throttling (not blacklisting and
  # whitelisting). It must implement .increment and .write like
  # ActiveSupport::Cache::Store

  # Rack::Attack.cache.store = ActiveSupport::Cache::MemoryStore.new

This looks like a pretty good gem for handling the connection/configuration: https://github.com/redis-store/redis-rails

[ktheory]

Yeah, if you have config.cache_store = :redis_store in your Rails app, there's no additional configuration for Rack::Attack.

If that's not clear, a PR improving the documentation is welcome. Thanks! 😎

[MarkMurphy]

@ktheory @zmillman Thanks, much appreciated. I've been using Rack::Attack for a few months now and the reason I'm now looking to change the cache store is because this gem eats up large amounts of space on my server via cache files it stores on the filesystem. The documentation really should make it more clear that when using this gem, you should be using something other than the default rails cache and why.

[fluxsaas]

here is an example, which helped me:

https://gist.github.com/ktheory/5087320

not sure if that is the best way to include ist.

or you could use the Rack::Attack::StoreProxy::RedisStoreProxy if you have Redis.current hooked up to a Redis server:

Redis.current = Redis.new(host: ENV['REDIS_HOST'], port: ENV['REDIS_PORT'])

class Rack::Attack
  Rack::Attack.cache.store = Rack::Attack::StoreProxy::RedisStoreProxy.new(Redis.current)
end

[Chrisgo-75]

Thank you @fluxsaas. You helped me with figuring out how to configure Rack::Attack to use Redis as its caching mechanism.

# File: rack_attack.rb
class Rack::Attack
    Rack::Attack.cache.store = ActiveSupport::Cache::RedisStore.new("redis://example.com:6666/0/cache", { expires_in: 480.minutes })
    ... ...
end

[waruboy]

@fluxsaas exactly what I need. Redis connection to RedisToGo on heroku app. Thanks!

[saygun]

Those who faced same problem in Rails 5 might check

config/development.rb

config.cache_store = :null_store # comment out this one

[Skillvendor]

@saygun You have no idea how much i love you

[lordplagus02]

Is there a 2020 method for this or have the solutions remained the same?

[grzuy]

Hi @lordplagus02,

Since v5.4.0 (https://github.com/kickstarter/rack-attack/blob/master/CHANGELOG.md#540---2018-07-02) you can connect rack-attack directly to redis by setting the store to the Redis client:

Rack::Attack.cache.store = Redis.new(...) 

[Aryk]

Does this library automatically set expirations on the redis objects. LIke for example, if we have a "period" of 5.minutes on some throttling. After 5 minutes that key is gone right? Or is there no purging mechanism?