Home/ Questions/Q 299105
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T06:47:33+00:00

environment.rb: config.cache_store = :mem_cache_store, ‘127.0.0.1’, { :namespace => RAILS_ENV.to_s } development.rb: config.action_controller.perform_caching = true

  • 0

environment.rb:

config.cache_store = :mem_cache_store, '127.0.0.1', { :namespace => RAILS_ENV.to_s }

development.rb:

config.action_controller.perform_caching  = true

This is the memcached output when I call the url.

get development:views/127.0.0.1:3000/aktionen.xml sending key development:views/127.0.0.1:3000/aktionen.xml END set development:views/127.0.0.1:3000/aktionen.xml 0 60 3 STORED

Controller

caches_action :index, :expires_in => 5.seconds, :layout => false, :format => :xml

Info

cache_pages produces no memcached activity at all. Rails writes aktionen.xml to the public folder, also ignoring expires_in and format parameters. Calling 127.0.0.1:3000/aktionen creates a aktionen.html file

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Rails (as of 2.1) provides different stores for the cached data created by action and fragment caches. Page caches are always stored on disk.

    Action caching is VERY similar to page caching, the only difference is that the request for the page will always hit your rails server and your filters will always run. To setup action caching our controller might look like this:

    class BlogController < ApplicationController
  layout 'base'
  before_filter :authenticate  # <--- Check out my authentication
  caches_action :list, :show

    More info here: http://railsenvy.com/2007/3/20/ruby-on-rails-caching-tutorial-part-2

    • 0