memcache on Heroku's cedar stack in Rails 3.1
Join the DZone community and get the full member experience.Join For Free
If you're building a Rails site, you almost definitely need to have caching. memcache is the best solution for that problem right now. It's not too hard, but there are only bits on the internet on how to do it.
Install memcache addon
$ heroku addons:add memcache
Install memcache locally
$ sudo port install memcached # for macports $ brew install memcached # for homebrew $ sudo apt-get install memcached # for ubuntu/debian
Put the 'dalli' gem into your Gemfile (this is the memcache driver) and run the 'bundle' command
<span class="comment"># Gemfile</span> gem <span class="string"><span class="delimiter">'</span><span class="content">dalli</span><span class="delimiter">'</span></span>
In production.rb and development.rb, set the cache_store
# /config/environments/production.rb config.cache_store = :dalli_store
# /config/environments/development.rb config.cache_store = :dalli_store
Now change your session initializer (for memcache session support)
# config/initializers/session_store.rb require 'action_dispatch/middleware/session/dalli_store' YOURAPPNAMEHERE::Application.config.session_store :dalli_store
How this works
This works without setting any configuration since dalli will connect to the MEMCACHE_SERVERS environment variable, which gets set when you install the addon. If that environment variable is not present, it will connect to localhost (which works for development).
Dev environment troubleshooting
The most common error you will see is dalli not being able to connect. First, make sure that memcache is running. For that, I like to use telnet to connect to the local running memcache service. It's kinda fun too!
$ telnet 127.0.0.1 11211
Then you can do:
SET foo bar GET foo
(should return bar)
Still running into problems?
I've ran into a problem on Vagrant and a Windows development installs where Dalli would not be able to find the local running memcache service. For that, I found that setting the host to '127.0.0.1' fixed the problem. I imagine it's something to do with IPv6, but I'm not sure.
So to fix, just do
$ export MEMCACHE_SERVERS=127.0.0.1
That worked for me!
Opinions expressed by DZone contributors are their own.