Blog Posts under "Django" Five posts

After much tweaking, hand-wringing, and thumping around on staging, django-dynamodb-sessions is ready. The package provides a super-high-scalability session store for those hosting on Amazon's EC2.

This may be useful to you if...

You're wanting to trim your DB size, or reduce the read/write thrashing that happens with DB-backed sessions. You also don't feel like maintaining Redis, or something similar.

With the introduction of Amazon's DynamoDB, we now have a very fast, massively scalable data store that is somebody else's problem to secure, update, and keep running. I've found the response times to be great, especially when combined with the provided cached_dynamodb backend (similar to Django's cached_db backend).

This probably isn't a ...

When a free service or module proves to be invaluable to your project(s), it's only right to thank the authors for their excellent work. I thought I'd take a brief moment to thank all of the contributors behind Read the Docs for this simple but wonderful site. I have found it to be extremely useful for my hobby and real-world projects.

For those who have yet to see the light

If you have Sphinx-based documentation and haven't played with Read the Docs yet, I can't recommend it enough. Not only do you not have to hassle with hosting your compiled HTML documentation yourself (or on a specially named branch in VC), you can point ...

I've obviously been on a bit of a proxied MUD server tangent of late (see here and here). I typically haunt #evennia on FreeNode, and brought the point up to the current maintainer, Griatch, a few weeks ago. As is typical for Griatch when he finds something he likes, he cranked out his take on an AMP-based proxy (the Evennia term is "portal") very quickly, and announced the specifics a few days ago.

The biggest benefit in the case of Evennia is that the old, complicated code reloading system is now completely gone. This is a big win in simplicity and avoiding nasty edge cases where reloading doesn't work as expected.

For those that haven't heard ...

This is a quick tip that will hopefully save someone else a few minutes at least. If you're using Django 1.3, using pylibmc and want to point at a local unix domain socket for memcached, this is what your CACHES setting will look like:

    CACHES = {
        'default': {
            'BACKEND': 'django.core.cache.backends.memcached.PyLibMCCache',
            'LOCATION': '/tmp/memcached.sock',
        }
    }

This also assumes that you have configured memcached to use a unix domain socket (with the -s option in memcached.conf).

I run an Arch Linux desktop as my primary development workstation. We use celery pretty heavily on some of our Django projects, and I was working to get my local environment at least somewhat closer to our production setup, only to find there isn't a non-AUR package for rabbitmq-server.

Of course you can just download an AUR package, but that's not nerdy enough. I managed to get a GitHub project to act as a pacman repository, and will share it here in case anyone else would like to stay up to date with rabbitmq-server without mucking with the AUR packages yourselves.

Just to be clear, there is no real benefit to installing from my repository, other than not ...