#25748: Glossary: Project vs App
-------------------------------+--------------------
     Reporter:  guettli        |      Owner:  nobody
         Type:  Uncategorized  |     Status:  new
    Component:  Documentation  |    Version:  1.8
     Severity:  Normal         |   Keywords:
 Triage Stage:  Unreviewed     |  Has patch:  0
Easy pickings:  0              |      UI/UX:  0
-------------------------------+--------------------
 There are several blog posts and stackoverflow answers about this topic:

 "Project" vs "App".

 I would like to see an official statements about these terms.

 I checked the current docs and could not find a definition. I hope I was
 not blind :-)

 What is an "app" and what is a "project"?

 Here is what I tell new team mates:

 Project: A project is a container for app. It contains only settings, no
 database models. Since it contains no database models it does not contain
 database schema migrations. It can contain migrations which fill a
 database with project specific data. A project might contain a
 sitecustomize.py


 App: An app has models, views and code. It should be re-usable. An app can
 depend on an other apps. It must not depend on a project. An app can
 contain a settings.py for testing, but it has no settings on its own. It
 should have instructions which settings are needed to get the app running
 in a project. A app must not contain a sitecustomize.py.

--
Ticket URL: <https://code.djangoproject.com/ticket/25748>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" 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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.4a9a2b2cf664b3272f5742f61bccbfe7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to