Am 23.08.2016 um 14:11 schrieb Michal Petrucha:
Finally, you need one Python package that serves as the “app” that
glues all the other packages together. This is the package (or app)
that contains the settings module, the root URL configuration, the
WSGI entry point, and often also static files, templates, views and
other stuff that only make sense in the context of the project itself,
and cannot reasonably be spun out into a separate package (that would
be things like the base template, or sometimes the landing page view).
This is what you referred to as the “project-under-the-project”.
The reason why this is inside a separate subdirectory is that you want
Python to be able to import it.
I cannot remember where is was stated, but iirc another reason for the
“project-under-the-project” subdirectory was that it is considered not as app,
but rather as “site”.
That is, if you deployed the same project in a different context (with different
configuration), you would have another such “site” directory, e.g.
clientmanagement/clientmanagement-internal/ or
clientmanagement/test-other-webserver/ etc.
Best regards,
Carsten
--
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 django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/be36f2a7-8f38-9c5d-3a90-b836aead863b%40cafu.de.
For more options, visit https://groups.google.com/d/optout.
