Big admin improvements
I've committed a change that fixes ticket #627. The Django admin app has been refactored, to make things simpler and tighter -- both conceptually and in code layout.
The major change is that an admin site no longer requires its own settings file. Yes, you can run the admin and "main" sites off of the same Django installation!
This should eliminate the problem that some newbies have in keeping track of whether they're using "myproject.settings.admin" or "myproject.settings.main." Now it's just "myproject.settings." Plus, instead of "myproject.settings.urls.main" and "myproject.settings.urls.admin," it's now just "myproject.urls."
The whole thing just got a heckuva lot simpler. :)
Unfortunately, this was impossible to do without breaking backwards-compatibility. I've outlined all the code changes you'll need to make on the backwards-incompatible changes page.
I've also updated the tutorial to reflect the changes. You might find it useful to read the tutorial again to note the subtle differences.
Feel free to post questions to the django-users mailing list.
Posted by Adrian Holovaty on October 18, 2005
Comments
wgunadi at nextcoder.net October 20, 2005 at 12:31 p.m.
I was wondering how to deploy my Django-based application which uses the Admin interface to manage User and Roles. Do I need 2 servers? well, this is the answer! Good job, Django team!
jvoorhis October 20, 2005 at 2:05 p.m.
Adrian: Thank you! I was having some apache configuration troubles with the two installations. This should be nice.
Comments are closed
To prevent spam, comments are no longer allowed after sixty days.
W Brown October 19, 2005 at 9:51 a.m.
You read my mind. I just finished going through the tutorial yesterday and thought that I would spend most of my day today trying to figure out how to get the admin and the main site to work together. Thank you.