I've read this, but I'm not sure how to reset connections to memcached. I've tried doing: Rails.cache.reset, but that's not a defined method.
This line: CACHE = MemCache.new 'localhost:11211' Also does not work when I put it in my production.rb. I get an error that says I have an uninitialized constant Rails::Initializer:MemCache I've installed the memcache-client gem. All documentation says rails automatically tries to require it, in fact it's already built into rails already. So I try to just use the Rails.cache object, which has nothing the gem docs says it has. How do I reset Rails.cache? On May 4, 10:52 am, Rama <[email protected]> wrote: > This should help you understand the problem: > > http://www.modrails.com/documentation/Users%20guide.html#_example_1_m... > > Has a little tip on what you could do when you fork... > > Rama > > On May 4, 12:23 am, kineticac <[email protected]> wrote: > > > Is this the right place to post help for memcached and rails apps? > > > My rails app is running great in development with memcached, but when > > I tossed it up on production, with the exact same setup, it stopped > > working with very little error messaging. > > > I'm using Phusion Passenger which runs Apache, Ruby Enterprise, > > memcach-client gem, and of course memcached. > > > I keep hearing about a lot of issues (inconsistent) with passenger and > > memcached, and then with REE and memcached, but can't seem to find a > > definitive answer to any of these. I feel like all production servers > > use REE, passenger, and memcached together more often then not. I'm > > not sure how to address these problems and what special items I need > > to setup. > > > If anyone has any info on what differences I need to take on a > > production server that might differ from my development? > > > Thanks
