This blog post is about deploying Django apps. It is addressed primarily to
WebFaction , but applies to any
other hosts else with one-click installers for this kind of app.
First, many thanks to WebFaction for their great service and support. I've got
very few complaints about them in general.
However, I think their approach to setting up Django projects is far from ideal,
and makes life harder than it needs to be.
The WebFaction Django docs tell us to
create a new Django app by using the control panel and choosing an app of type‘Django' and then choosing your Django version. This will install an Apache
instance with mod_wsgi, and a copy of the Django sources, and set up a basic
Django app skeleton.
There are lots of problems with this:
What happens when there is a security issue with Django?
The user will need to have an upgrade mechanism. This is covered in the docs,
but it is an 11 step process .
And this process is a process they will first have to do in their development
environment for testing, in some way, and then again on their live box. How
many people will actually do that, especially for security releases that they
don't feel they need?
Experienced developers, of course, don't do this. For Django, I've .. cntd
↧