Surfing in Kansas
« A start to the uber community | Gentlemans agreement on Django templates »
So at work since I started for Mediaphormedia, currently World Online, and the birthplace of Django, I have been tasked with porting Ellington. Ellington is the CMS that we create and sell, and is what Django originally was. Django was pulled out of Ellington and Open Sourced.
So when I got here, my first job was tasked with porting Ellington. We have a version running on Revision 1290 and .91. Aka, really damn old, pre-magic removal old. We were tasked with porting this to Django 1.0 (which is around revision 9300). That is a whole 8000 source code revisions, and 600% more revisions than the base. That is a whole lot of code.
So today at work, we are launching our 3 main sites; Ljworld, KU Sports, and Lawrence.com. These will be running all on Django 1.0, which is a monumental task.
That is the reason today's post is short. Was bug fixing all day, and I have to be up at 5am to go in and put out the fires that will surely happen once users start hitting the site.
I will have an updated post afterward about the experience.
Comments have been close for this post.
Posted at 9:42 p.m. on November 17, 2008
Comments: 0
Tags: ellington , mediaphormedia , post-a-day
Django Inspect: A generic introspection API for Django models
4 weeks Ago (Comments: 4)
The role of designers in the Django community
1 month Ago (Comments: 7)
Large Problems in Django, Mostly Solved: Documentation
1 month, 1 week Ago (Comments: 5)
2 months Ago (Comments: 0)
Correct way to handle default model fields.
3 months, 3 weeks Ago (Comments: 8)
I may not have gone where I intended to go, but I think I have ended up where I intended to be.
- Douglas Adams
