Deployment strategies for the lean generation
If you deploy little and often, two things happen - first, you get a lot better at it, and second, you get to a point where it's easier to fix a deployment issue and redeploy than to attempt a rollback.
If you work in or around a corporate IT department for any length of time you'll get used to hearing a lot about . . .
A brief walkthrough of the Django session and authentication middleware.
tl;dr If you already know how Django sessions and auth work, read no further - you won't learn anything new.
Coming from a .NET 'enterprise' background, one of the things that confused me at first about Django was the phrase . . .
Refactoring is important enough to be treated as a development activity in its own right and should not be shoe-horned in on the quiet along with other tasks
This post is partly an attempt to atone for my own sins (and apologise to @stevejalim), partly a public aide memoire to prevent me from doing it again.
In 20 years of . . .
Using mixins to add fluid filters to Django model managers.
There are plenty of samples on the web showing how to create custom Django
QuerySet and Manager classes to create fluid manager interfaces; here's
We have a lot of shared fields across models, that we filter on in similar
ways, . . .
In the third (probably not final) post on our deployment process, our Fabric
script has become intelligent enough to manage deployment options on our
Testing code that relies on remote APIs that themselves rely on OAuth can be painful, if not impossible. This is how we do it.
For all of its well-publicised issues, OAuth is a great step-forward for secure authentication / authorisation for granting access to remote APIs on by apps on behalf of users. We use OAuth to access LinkedIn . . .
We've upgraded our Fabric deployment scripts so that we can now see all of
the commits that will be pushed as part of the deployment.
As we mature as a company and a development team, our use of Fabric to script
basic tasks is also maturing. Our latest addition is to incorporate the git
changelog into the deployment . . .