Stephen John Smoogen wrote:
On Fri, Sep 12, 2008 at 11:23 AM, Michael DeHaan
<mdehaan(a)redhat.com> wrote:
> Michael DeHaan wrote:
>
> Someone pointed out to me that if I had concerns about TurboGears
> stability I should look at Django again.
>
> Anyhow, it is worth nothing that Django supports EL4, which is a win.
>
> Still to be explored...
>
>
I am looking at django right now as my learning project of the month.
how can I help?
Starting to port CobblerWeb to django (as is) would be how I'd start to
do it -- I think we'd find out along the way what the roadblocks would
be and where the framework would allow
us to clean up things that are already there. There would be some things
we'd have to get to eventually -- like making sure the auth modules
still work without (much) reconfiguration.
Once that was done we could look for ways to improve it.
All the code is in CobblerWeb.py (cobbler/web) and
webui_templates/*.tmpl presently though it need not be a 1:1 port
The main thing is we're going to be using Cobbler's XMLRPC for the
model, not so much the database. If cobbler does have a database, it
will be beneath cobblerd so the Web app won't have to know about it.
This essentially should be a seperate package just using the Cobbler
XMLRPC api.
We would not be porting anything served by /cblr/svc, just cobbler/web
URLs as well, so no reason to worry about those. They are
unauthenticated and meant for machines, not humans.
--Michael