August 25th, 2009
I love the thought of people building a business based on doing something good, and doublegreen.dk is just such a business. CO2 negative hosting environments for Danish customers might not be the largest scale project, but it’s a step on the way. It’s just like voting… your vote means something so small / medium scale environmental goodies also matters. It’s not just up to the big companies to make the changes, all though that would also be much appreciated.
So all your people with one and dandomain.. move.. the sooner the better.
Tags: environment, hosting
Posted in hosting | No Comments »
August 9th, 2009
Just when I get really tired with Drupal something happens that kindda pull me back in. It happened to me again yesterday. I have spend a lifetime building a customer website, and the final result is – from a technical stand point – not the most beautiful piece of work I have ever done, so I was already afraid when the client called me. Apparently the 7000 comments on the site was not a sign of the sites popularity. Just spam.
After some digging I found Mollom, which is a somewhat commercial module for Drupal and installed it. After spending about 10 seconds on creating a Mollom account (thanks for supporting openid so well), 30 seconds to installed the module and about a minutes to setup the module, the site was protected against spam. Now, 24 hours after setting it up, no spam comments have made it’s way through.
When complex modules that integrate with an entire system that deep just work out of the box you have to give it credit. It’s simply fantastic.
Tags: drupal, modules, mollom, spam
Posted in Uncategorized | No Comments »
July 30th, 2009
This is not intended to be a rant or even close to it. But I find myself with a problem so obvious that I’m annoyed by the lack of solution. I can’t be the only developer with this problem.
I use South to handle database structure migration and it works (for the most part) very well, and I’m happy to use it. One problem though. When you actually need to migrate backward and forward many times you will run into problems with missing fields in your Django models. Say, so have a field called “person” on a random model. You wish to rename this to “full_name”, so you write the straight forward migration to handle this and remove the field from your model. Now, if you wish to migrate back your code is outdated. This mean that you’ll be unable to use your Django system to inspect things or whatever you might wish to do.
The solution – from my point of view – for all of us using some versioning tool would be to bind the migration to a changeset and have the forward and backward migrations update the code as well. This is a bit more demanding to set up, but it’s properly the only solution you have if you want the possibility to migrate back and have a useable system.
If only I had the time to take a proper look at South to find the solution.
Tags: database, django, migration, south, versioning
Posted in Uncategorized | No Comments »
July 25th, 2009
Somehow I managed to get my iPod + Nike stuff out of sync with the real world. Apparently the iPod didn’t like handling 2 Nike censors and somehow the calibration got damaged.
Today I tried to calibrate the system so I could start a new running frenzy. So I selected 1.25km and ran it (measured it on a map beforehand). When the distance was completed my breain dead iPod said 0.7km, so I ended the calibration but got an error message like the following:
The distance you have chosen doesn’t match the distance completed.
Is it me who’s an complete ass here? Or would you think that the reason for people to calibrate the censor would indicate some error in the step to distance conversion? If the completed distance was correct. WHY CALIBRATE???
Tags: ipod, nike, running
Posted in Uncategorized | 2 Comments »
July 6th, 2009
On May 7 Jacob Kaplan-Moss wrote a blog post on djangoproject.com about the status of Django 1.1. One of the things you really like as a web developer using Django is:
We’ll ship Django 1.1 when it’s stable, and not a moment before.
This really makes sense and we love the django developers for it. But right after he writes:
Thanks for your understanding, and watch this space for updates.
There haven’t been any updates yet. And at that time – according to the blog post it self – there were about 50 open bugs. Now there is only one. Why in gods names haven’t there been any updates? We’re a lot of people waiting for the release and we understand why we’re waiting. At least give us something to read while we’re waiting.
Update: I regret to say it happening again. 8 days ago the 1.1 release candidate was born, and the promise was that we would see the final release if no show-stopping bugs where found in the mean time. As far as I can see in the issue tracker, no such bug has been found. But still no release, and more importantly, no blog post or other communication explaining why. I know it’s only one day overdue, but why not just make a blog post, a tweet.. something about the release status.
Update II: Fantastic. Django 1.1 was just released. Hopefully we’ll see regular updates in the future from the team.
Tags: django
Posted in django | No Comments »