Hi Kelly,
in principle, the Django admin is just a very big Django app that
provides you with a nice web-interface to edit the data in your
database.
That is also the reason that it is relatively hard to port it to App
Engine, since the database is very different here.
However, App Engine provides the so-called Administration Console,
which offers a Data Viewer.
With this Data Viewer you can also edit data in your database.
Once you have uploaded an application ("python manage.py update" in
app-engine-patch, don't forget to set your app-id in app.yaml), you
can access the Administration Console by browsing to
http://appengine.google.com/
To be fair, the Django Admin offers much more possibilities than the
Data Viewer, and is also much more advanced in regards to
customizability. Therefor a lot of people are looking forward to a
complete implementation of the Django admin on App Engine.
But since it's only a (very advanced) Django app, you can re-create
the functionality you need yourself, and it is very possible to write
your app without using the admin.
If you have just started to learn Django, I recommend the "learning by
doing" approach, since it's not really hard to use it once you have
learned the basic principles.
You can find some Django sites with complete source code here:
http://www.djangosites.org/
If you are planning to use Django on App Engine, I would recommend to
get the app-engine-patch sample project and adjust it. The only real
difference to normal Django is the model definitions.
Jesaja
On Fri, Jan 30, 2009 at 11:36 PM, metametagirl <[email protected]> wrote:
>
> Hi Jesaja,
>
> Thanks for the explanation. Since I'm trying to do Django 1.0 on GAE,
> it's not always clear to me when to stop doing the steps in the Django
> tutorials (i.e. when it says to do 'python manage.py syncdb'.
>
> This also explains why the app-engine-patch docs say certain
> django.contrib apps a re only "available in repository". I didn't
> know what repository the doc was referring to, since I didn't realize
> you could download revisions directly from the repository. I prefer
> to use revisions that are not still under development so I guess I'll
> be skipping the admin functionality until I really need it. (At this
> beginning stage, it is not entirely clear to me what the admin
> functions are, but hopefully that will become clearer to me soon)
>
> Thanks again,
> Kelly
>
>
> On Jan 30, 1:51 pm, Jesaja Everling <[email protected]> wrote:
>> Hi Kelly!
>>
>> You don't need the syncdb command with app-engine-patch, since unlike
>> mysql, the necessary datastore "tables" will be created on the fly.
>> I haven't really used the admin in app-engine-patch myself yet, but I
>> have seen it work in the sample project that is provided with
>> app-engine-patch.
>> To use the admin, however, you must use the repository version of
>> app-engine-patch, the latest release doesn't yet include the admin.
>> When you click the "Source" tab on the project page, you will find a
>> link to the different Mercurial repositories that app-engine-patch
>> uses.
>>
>> http://code.google.com/p/app-engine-patch/wiki/GettingTheSource?tm=4
>>
>> You will probably want to check out the sample project. You can either
>> install a Mercurial client and clone the repository, or can use the
>> download-option that bitbucket provides.
>> Be aware, however, that you are using a version that is under constant
>> development now, so things might break when introducing new features,
>> or some things may be incomplete.
>>
>> Best Regards,
>>
>> Jesaja Everling
>>
>> On Fri, Jan 30, 2009 at 7:44 PM, metametagirl <[email protected]> wrote:
>>
>> > I'm trying to start a new app using Django 1.0 with the app-engine-
>> > patch. I'm used to using MySQL but I'm new to this datastore. The
>> > Django tutorial says to run 'python manage.py syncdb' to create the
>> > tables, but this doesn't work for me in my development environment.
>> > Is this step necessary when using this combination of technologies
>> > (Django 1.0 + app-engine-patch)?
>>
>> > Also, how do you invoke the Django admin in the development
>> > environment? My understanding is that it won't work once you upload
>> > the app to GAE, but that there should be a way to make it work in the
>> > dev environment.
>>
>> >> python manage.py syncdb
>> > WARNING:root:Could not read datastore data from /var/folders/bz/
>> > bzgZyG4mE5adBq+imZYFdk+++TI/-Tmp-/django_myapp.datastore
>> > WARNING:root:Could not initialize images API; you are likely missing
>> > the Python "PIL" module. ImportError: No module named PIL
>> > Unknown command: 'syncdb'
>> > Type 'manage.py help' for usage.
>>
>> > Thanks in advance,
>> > Kelly
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
