Better Local Settings — January 5, 2010

A common convention I've seen in the Django community is to place code like the following at the bottom of your settings file: # ``settings.py`` # Lots of typical settings here. # ... then ... try: from local_settings ... [Read More]

Launched!

Posted by Daniel on November 18, 2008.

As a point of historical note, the sites that caused Django to be created, LJWorld, Lawrence.com and KUSports.com have all launched on Ellington running on Django 1.0! It's been a long process to get here, and we have a little ways to go yet, but this is a very satisfying moment.

3 Comments

Awesome! Congratulations, I know that must have been a ton of work. How much of the conversion was automated in the end?
Posted by Simon Willison on November 18, 2008 at 8:05 a.m..
Congratulations!! It's great news.

Btw - have you noticed any efficiency and speed differences between previous and current Django/Ellington codebase?
Posted by Jakub on November 19, 2008 at 12:14 p.m..
@Simon - Code conversion tools got us about 35-45% of the way, though basically the entire codebase needed a once-over. DB conversion tools got us about 60% of the way, with lots of custom SQL needed from there.

@Jakub - Performance is better overall. We're seeing reduced RAM usage and the QSRF improvements have made a difference (especially when paginating and dealing with larger sets).
Posted by Daniel on December 16, 2008 at 10:05 p.m..

Sorry, comments have been closed on this post.