Django on Google Appengine using app-engine-patch

Posted: August 5th, 2009 | By | Filed under: Development | Tags: , | No Comments »

Edit 2014-01-23: The information on this post is extremely outdated! Please refer to the official App Engine cloudSQL documentation, or this article about using django-nonrel, or search for up to date information.

After writing about google-app-engine-django (read it for some introductory material about App engine and Django), I’ve found out now about app-engine-patch. This is another option of easily developing Django applications targeting Google App Engine.  App-engine-patch offers some significant advantages and features:

  • Support for a much greater portion of Django stack. Maybe most noticeably the Admin site works out of the box, which is great. Also, authentication, flat pages, mail functions, session and cache, generic views and more are supported.  All these are wrapped to use google-app-engine backend while maintaining high level of compatibility with django. Impressive.
  • Their last release supports the latest release of Django, version 1.1.
  • Additional handy librariers are provided (and some are used by the patch itself): Easy Django-ish query interface for google models (RagendjaDB), Componenet zipper (for faster uploading and loading on app-engine), Media generator (merges CSS and JS files), and others.
  • Remote administration of the data model is supported (haven’t tried it yet). Basically, you can run “manage.py  shell” and work on the remote DataStore models. Can be very useful for maintainance of your live application, or importing/exporting some data there.
  • The project seems under very active development. and quite a few slick sites in production are using it.
  • Installation was very easy. Their recommended mode of installation is just unpacking their very minimal sample application, modify a couple of settings file, remove what you don’t need and get it on. Oh, I also had to link or copy app-engine SDK to /usr/local/google_appengine.

So, all in all, I’m very impressed by the level of support for Django the project has reached, and it seems like the natural choice for doing Django development on google app engine at the moment.

facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Leave a Reply