it seems that i need to time and practice to get that logic, my old way was using the same code and import it like a normal module (as a file and not as a whole structure).
Le dimanche 25 janvier 2015 20:49:20 UTC+1, Jorge Andrés Vergara Ebratt a écrit : > > You can make one, but imagine having 12-15 apps and managin all of them in > one admin.py file, that would make debugging harder, the admin.py per app > approach helps you keep all of your app's login inside the app, makes it > easy to re-use it > > On Sun Jan 25 2015 at 2:47:18 PM Aliane Abdelouahab <[email protected] > <javascript:>> wrote: > >> ah! because the admin in my mind was something i manade the entries? >> something like database management interface, then it would be easier to >> make it general of the global application, no? >> >> Le dimanche 25 janvier 2015 20:07:25 UTC+1, Kristofer Pettijohn a écrit : >>> >>> Your admin.py is specific to each app, on how you want the models for >>> your app to show up (or not show up) in the admin page. >>> >>> Each app's admin.py will be unique to the models specific in that app. >>> >>> The tutorial in the Django documentation shows a good example. >>> >>> ------------------------------ >>> >> *From: *"Aliane Abdelouahab" <[email protected]> >>> *To: *[email protected] >>> >> >>> *Sent: *Sunday, January 25, 2015 10:59:09 AM >>> *Subject: *Why using admin.py in apps? >>> >> Hi, >>> My question seem dumb, but what is the purpose of repeating the admin.py >>> in the apps? >>> >>> as i understand, if i want to have a good practice, i separate my >>> application on mini apps so i can re-use them, and one of the apps that is >>> always used, are Logins (Registrations), so, why i have to repeat the >>> admin.py for every app, since the admin.py is related for the big project >>> (startproject), and not for the small application (startapp) (login here) ?! >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django users" group. >>> >> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> To post to this group, send email to [email protected]. >>> >> >>> Visit this group at http://groups.google.com/group/django-users. >>> To view this discussion on the web visit https://groups.google.com/d/ >>> msgid/django-users/99db6624-f50c-420c-81d6-89efa42286d2% >>> 40googlegroups.com >>> <https://groups.google.com/d/msgid/django-users/99db6624-f50c-420c-81d6-89efa42286d2%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at http://groups.google.com/group/django-users. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/442b55d8-1a3d-440f-859b-6751b6d69f50%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-users/442b55d8-1a3d-440f-859b-6751b6d69f50%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/0c813a4b-1793-4bcb-801a-02e324a2bdcd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
