It’s pretty much a drop-in replacement for StaticGenerator except that you need to edit your settings.py to use memcached as cache backend.

CACHE_BACKEND = 'memcached://127.0.0.1:11211/'

And of course you need to update your nginx config. It could look like something like this:

# This example configuration only shows relevant parts
# It assumes your django app is served via http on localhost:9004
location / {
    #pass POST requests to django
    if ($request_method = POST) {
            proxy_pass http://localhost:9004;
            break;
    }
    default_type  "text/html; charset=utf-8";
    set $memcached_key "$host$uri";
    memcached_pass localhost:11211;
    error_page 404 502 = /django;
}

location = /django  {
    proxy_pass http://localhost:9004;
    break;
}

I tried to cover everything in the README.

Bonus feature!

I included one bonus feature not exisiting in StaticGenerator. You can add the following line to your settings.py which will make StaticGeneratorMem not to put responses in memcached if there is any user logged in.

STATIC_GENERATOR_ANON_ONLY = True

You can the modify your nginx config to something like this. Note that you need to edit the domain field for your settings id in your database to reflect the server_name which is used in the memcache key. You can also set it as SERVER_NAME in settings.py if you are not using contrib.sites.

# This example configuration only shows relevant parts
# It assumes your django app is served via http on localhost:9004
location / {
    #pass POST requests to django
    if ($request_method = POST) {
            proxy_pass http://localhost:9004;
            break;
    }
    #pass logged in users to django
    if ($http_cookie ~* "sessionid=.{32}") {
        proxy_pass http://localhost:9004;
        break;
    }
    default_type  "text/html; charset=utf-8";
    set $memcached_key "$host$uri";
    memcached_pass localhost:11211;
    error_page 404 502 = /django;
}

location = /django  {
    proxy_pass http://localhost:9004;
    break;
}

And logged in users will hit the django app with a dynamic request instead of the cached content in memcached. If you changed the cookie name of your session id to something else than sessionid you need to take that into consideration aswell. From my experience this doesn't work 100%, if a user logs out the cookie usally remain with an invalid session id which will cause logged-in-and-then-logged-out users to hit the django app directly and not cached content. On a blog or content heavy site which is StaticGeneratorMems primary usage this would only be you and any other authors so it's probably not a big deal, just something good to know.

Should I use this or StaticGenerator?

This is totaly up to you. Both will give you excellent perforemence boosts though StaticGenerator will give you the best performence. If you prefer puting cached things in memcached, using StaticGeneratorMem is a neat way of doing it. With StaticGeneratorMem a restart of memcached and the cache is gone. More on this in my previous post about this.

That's all for know. Remember to tail your apache (or whatever httpd you are using) access log side by side with your nginx acceess log to make sure that only the first request hits both servers and the second only nginx. I'd be glad for any feedback on this.