I generally call applications that are primarly database backed by the most important table's name unless another name is immediately more obvious. So if the site is a webcomic then call the app comics. If it is a song lyric website call it lyrics. Otherwise there shouldn't be a particular problem with calling it main or base or whatever. You may find later that you can refactor it into more applications.
On 20/09/06, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > > gabor wrote: > > so, how do you name your 'main' app in a django-project? > > For me it depends on project's type. > > If a project is autonomous and serves one purpose then, yes, I call the > main app 'main' and it could even be the only app in the project. > > If a project is multi-purpose and just powers a whole site or many parts > of it then there is no concept of main app at all and all apps are named > by their function. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users -~----------~----~----~----~------~----~------~--~---
