Re: When do we stop using Django admin?

I tend to use the Admin for internal tasks - ones that would be performed by a application or system administrator. These are people that understand the data structure and know things like the effects of a cascaded delete. For users, even a customer 'admin' person, I would write my own views

Re: When do we stop using Django admin?

On Mar 8, 8:16 am, ajaishankar wrote: > Thanks Viklap > > We have been doing a lot of ModelAdmin & ModelForm tweaking as > mentioned in those slides. > > But still kind of skeptical we should be opening up the admin to other > companies; and go through the gymnastics of

Re: When do we stop using Django admin?

Thanks everyone for your valuable suggestions! On Mar 8, 3:23 am, Michael Radziej wrote: > On Mon, 7 Mar 2011 21:49:45 -0800 (PST), ajaishankar > wrote: > > I do know we can tweak the admin to restrict querysets etc. and also > > override admin

Re: When do we stop using Django admin?

On Mon, 7 Mar 2011 21:49:45 -0800 (PST), ajaishankar wrote: > I do know we can tweak the admin to restrict querysets etc. and also > override admin templates - but is admin preferable in this situation? > > Or is it better to treat all this as a front end web app, and

Re: When do we stop using Django admin?

Agree, Admin should be considered as Admin for internal stuffs. if there is lots of opening up required. you should treat it as a customized app. Opening up of a table or two might work good in admin itself, with not much relations. Regards, //Vikalp On Tue, Mar 8, 2011 at 11:46 AM,

Re: When do we stop using Django admin?

Thanks KG :) On Mar 8, 12:16 am, ajaishankar wrote: > Thanks Viklap > > We have been doing a lot of ModelAdmin & ModelForm tweaking as > mentioned in those slides. > > But still kind of skeptical we should be opening up the admin to other > companies; and go through the

Re: When do we stop using Django admin?

On Mon, 2011-03-07 at 21:49 -0800, ajaishankar wrote: > I do know we can tweak the admin to restrict querysets etc. and also > override admin templates - but is admin preferable in this situation? no > > Or is it better to treat all this as a front end web app, and start > work on fresh pages.

Re: When do we stop using Django admin?

Thanks Viklap We have been doing a lot of ModelAdmin & ModelForm tweaking as mentioned in those slides. But still kind of skeptical we should be opening up the admin to other companies; and go through the gymnastics of restricting say a foreign key lookup to just the data they are allowed to

Re: When do we stop using Django admin?

Hi, Django Admin is nicely structured to give you lot of flixibility. We have tweaked around admin using all possible features and with good mingling of MIDDLEWARE, AUTH_BACKENDS and STORAGE one can achive a lot of integrations and customizations. have a look at these slides, it brings more

When do we stop using Django admin?

Hi We have a app built on Django, and have been using the admin to good effect. Right now we want to open up the app to other companies: 1. They can log in, create *their* own users 2. They can only see data that belongs to their company etc. 3. Also in one part of the app, we expect a highly