Julian's picture

Are there any plans to release a version of Turnkey Django with python-django version 1.2? 

Currently it uses 1.1.1 but there are lot's of new features in 1.2.

Alternatively is it easy to upgrade django to 1.2 on the turneky box once it's installed?

Many Thanks



Don Sanderson's picture

package management an upgrade should work.

To test this run dpkg -l django, it will show the package version if it was installed this way.

If it was installed from source it won't.

If it was through package management , and a new .deb package is available for Ubuntu 10.04 download it and run: dpkg -i django.xxxxx.deb to install it.

If it was installed from source things get a bit sticky and I'd have to look over the appliance to see what is involved.

IN ALL CASES use tklbam-backup to do a full backup first! :-)

Jeremy Davis's picture

Not yet anyway. ATM TKL Django uses the Ubuntu packaged version from the main repo. This means that it gets guaranteed security updates (automatically in TKL) until 2015. From a dev (maintenance) perspective that upstream support is hard to walk away from.

Having said that I notice that 1.2.1 is in the backports testing PPA so it should make it's way into the official backports repo eventually. Until then you could add the PPA to your repos and help them test. I'm not sure about the updates in the backport repo though. Even though it's an official repo I think they are only community supported (like universe and muliverse) so no guarantees on timely security updates AFAIK.

evilzar's picture



it could be interesting migrating directly the appliance to 1.3 version, could't?



Jason's picture

Since it looks like it might be a while before Django 1.4 will arrive on TurnKey Django any time soon, might someone be able to provide some detailed steps in how to uninstall 1.1 and install 1.4?

I started with the instructions at https://docs.djangoproject.com/en/dev/topics/install/?from=olddocs#remov... but kept running into problems because I don't know how Django was installed and it seems that many of the files end up in places that aren't the default for the stock Django install proceedures.

I'm pretty new to Django and very new to Apache server configuration so if the steps aren't spelled out pretty clearly, I'm afraid I'll be lost.

It occurred to me that I might be better off starting with the TurnKey LAMP stack then installing Django (which I'm doing now), so if that is the best approach, I'll continue down that path.

Thanks for the great product!



Jeremy Davis's picture

Otherwise if you still want to remove old Django from the appliance then I'm pretty sure it's installed with package management so remove it like this (assuming you have your data and settings backed up):

apt-get --purge remove django

Jason's picture

Jeremy, thanks for the tip but it seems like Django was not installed using a package manager becuase that command only generates "Couldn't find package django". My attempt using the LAMP stack was sidetracked because the version of Apache included in that Turnkey appliance wasn not built correctly to allow use of mod-wsgi. I can't remember the details at this point but I kept running into roadblocks during my attempt to build Apache with all the right components and I was just getting way out of my element. I'll keep trying other options and report back with any progress.


Jeremy Davis's picture

It seems the package name is python-django. Try removing that. For future reference, on the appliance page it says that it's installed from package management so I had a quick look at the appliance manifest (link on appliance page) and did a text search for django...

PS mod-wsgi should be installable from packagem management although I haven't confirmed. This is for an older version of Ubuntu but is hopefully still relevant:


rottinkulo's picture

Why are they not udating the Django appliance to use Django 1.4?????

There have been major changes in the layout of the directories and most of all in the packages!

I have been spending three bloody days trying to figure out how to move on to 1.4 from the present one on the appliance.

To no avail!

Gosh, life should be simpler sometimes... is it not one of the purpose of using an appliance?


Jeremy Davis's picture

I would suggest you base on LAMP appliance. Because it is much higher maintenance to install from upstream (and therefor much more secure to use Debian packages - they are maintained by Debian developers and have security patches backported) by the time TKL release an appliance with Django 1.4 is released it too will be 'out of date'. I'm guessing that there is some fnctionality missing in the installed version?

Perhaps you should consider seeing of others are interested in working together to create a Django 1.4 patch that you can then all share....!?

Add new comment