Changes between Version 40 and Version 41 of AppEngine


Ignore:
Timestamp:
Jun 22, 2015, 4:40:03 AM (9 years ago)
Author:
Ola Sitarska
Comment:

Added extended information about Djangae -- alternative to django-nonrel

Legend:

Unmodified
Added
Removed
Modified
  • AppEngine

    v40 v41  
    11= Django on AppEngine =
    22
    3 Django can run natively on Google App Engine using Django-nonrel
     3Django can run natively on Google App Engine in two ways:
    44
    5 https://developers.google.com/appengine/articles/django-nonrel
     5- [https://developers.google.com/appengine/articles/django-nonrel using Django-nonrel] -- a Django fork that supports non relational databases
     6- [http://djangae.readthedocs.org/ using Djangae] -- a Django app that allows you to run Django applications on Google App Engine with vanila Django
    67
    7 Parent wiki page: NonSqlBackends
     8=== Djangae ===
     9
     10Djangae (djan-gee) is a Django app that allows you to run Django applications on Google App Engine, including (if you want to) using Django's models with the App Engine Datastore as the underlying database. Djangae supports Django 1.6 and 1.7, with 1.8 version being under development.
     11
     12[http://djangae.readthedocs.org/en/latest/ Documentation] [https://github.com/potatolondon/djangae Github] [https://potatolondon.github.io/djangae/ Website]
     13
     14==== Features ====
     15
     16* A WSGI middleware that provides a clean way via which your Django app is plugged into App Engine.
     17* A hook to allow App Engine's deferred tasks and mapreduce handlers to run through the same environment.
     18* The ability to use the Datastore as the database for Django's models. You can also use App Engine's NDB, or you can use Google Cloud SQL (via the standard django MySQL backend) instead of or along side the Datastore. Or use all 3!
     19* djangae.contrib.gauth which provides user models (both concrete and extendable abstract versions), an auth backend, and a middleware; which allow you to authenticate users using the App Engine's built-in Google Accounts authentication, and also allow you to use Django's permissions system on the Datastore (i.e. without being caught out by the Many-To-Many relationships).
     20* A runserver command which fires up the App Engine SDK to serve your app (while still using Django's code reloading).
     21* The ability to run management commands locally or on the remote App Engine Datastore.
     22* A shell command that correctly sets up the environment/database.
     23
     24
     25Parent wiki page: NonSqlSupport
Back to Top