A look at how to manage deployment complexity with Django using Fabric. Something of a continuation on the post from yesterday.
When I develop with Django I'm constantly searching documentation, trying to figure out new modules and generally looking for answers to new problems as they arise. Today I'm introducing a new project, Findjango, which hopes to being a valuable resource for searching on Django-related topics.
One of the most common quickie projects on the web is to screenscrape a website and play around with its data. These projects are a lot of fun, and can allow for inventive mashups, but often the screepscraping scripts cause unnecessary load on the site's servers due to inconsiderate technique. This is an introduction to the art of compassionate screenscraping.
A simple but helpful trick for using optional parameters in Django views to allow one view to serve multiple urls with varying parameters.
Moving along in the Two-Faced-Django series, we look at using JQuery for Ajax in the webapp portion of our program.
The first example in the Loosely Coupled Django series, this entry looks at replacing Django's template language with the freshly released Jinja2 template language.
I've been working on a Facebook application with a couple of friends recently. We decided to use PyFacebook library, but there was a brief period of intense confusion on my part about how to use the PyFacebook library without the included middleware. I worked through it, though, and this article has some advice on how you can do the same.
The first article of an eight article series on using Django to create apps that exist simultaneously as independent web applications and as Facebook applications. This segment covers putting together our development setup.
The second example in the Loose Coupling in Django series. This one looks at a place where Django's loose coupling is at its tightest: the Django ORM.
Software engineer, technical leader, sci-fi reader, and so on. Born in NC, living in SF, and glad to grab a coffee.