A run of pickling problems with our tests has required us to delve into the rq and django-rq source code. If you run rq in synchronous mode, queued functions are run directly by the
enqueue method, but redis is still used to store 'job' information.
We use the redis -> rq -> django-rq chain to run all our async processes, and a . . .
Heroku's deployment model has always had a single point of frustration - the requirement to take the site offline, if only for a couple of minutes. In certain circumstances this is solved by the 'preboot' labs feature.
I love Heroku's simple git deployment model, and having lived with it for almost a year, I can't imagine . . .
Efficient workflow and task management using Trello
We've recently taken on a third developer (well, second developer, but I'm also counting myself), and our ad hoc workflow took a battering. So we upgraded.
As I have blogged previously, we use gitflow as our workflow, and as I may have mentioned, we use Trello to track what we're actually developing. When it was just @stevejalim . . .
Last week I finally managed to provoke our tech lead into using the 'F-word' in conversation. The trigger for this outburst was none other than HTTP status codes, and my desire to invent a new one. This was clearly beyond the pail.
I have since retreated from my original stance (a custom status code), but have committed a change to . . .
This is the opening doc that we share with new team members, outlining what
we expect of them in terms of coding standards and git etiquette. It's not
a lot more than 'be a good citizen', but thought some others may find it
First off, welcome aboard. This isn't a public project [ clearly this isn't
true, as . . .
Packaging Django-aware libraries for distribution
Packaging apps so that they can be tested within a django context, but without having to add them to an existing django project is pretty easy to to, but takes a bit more work than a standalone application.
We recently pushed our django-errordite and python-errordite apps to PyPI, and as part of that process I was keen to ensure that we . . .
Using Fabric and Git to manage Heroku environment configuration.
As previously discussed YunoJuno runs on Heroku. Doing so means adopting
their 12-Factor App philosophy, which has worked out great for us, and makes the project very clean in terms of separating code from configuration. One of its core tenets (and a requirement for hosting apps on Heroku) is the use of environment variables to store . . .