-
Notifications
You must be signed in to change notification settings - Fork 202
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
Configurable cache storage feature #234
Comments
Actually, you may not need to care about this. The cache is a cache, the cache of the RailsSetitngs like any other caches, we don't need to it for special. There is no reason need to do special. So why do you want storage RailsSettings's cache in a special place? Why not keep them in your Memcached (default Rails cache)? |
By you mentioned, why not let the And how large of your storage items in RailsSettings, is the reason is too big cannot storage that |
Let me clarify the issue. That's a common practice to have a distributed Rails application (i.e. with multiple RoR nodes running the same application) with separated caches (i.e. In this situation, to ensure some sort of consistency of |
There are some cases when one doesn't want to use
Rails.cache
to store settings cache, i.e. consider multiple rails nodes each using its own memcached server (so each node hasRails.cache
pointed to its own memcached node) -- for simplicity and consistency we'd like to use single shared redis server instance for settings caching.ATM
Rails.cache
is hardcoded so there's no way to override the storage.The solution is to make configurable option that can be set to any instance of
ActiveSupport::Cache::Store
(with default value ofRails.cache
)Are there any reasons this should not be implemented? If not, I'd be happy to provide a PR
The text was updated successfully, but these errors were encountered: