cms_local package¶
Subpackages¶
- cms_local.apps package
- Subpackages
- cms_local.apps.services package
- Subpackages
- Submodules
- cms_local.apps.services.admin module
- cms_local.apps.services.cms_plugin module
- cms_local.apps.services.cms_sitemaps module
- cms_local.apps.services.management module
- cms_local.apps.services.models module
- cms_local.apps.services.search_indexes module
- cms_local.apps.services.urls module
- cms_local.apps.services.views module
- Module contents
- cms_local.apps.support package
- cms_local.apps.services package
- Module contents
- Subpackages
- cms_local.templatetags package
- cms_local.themes package
Submodules¶
cms_local.routers module¶
-
class
cms_local.routers.
Router
¶ Bases:
object
A router to control all database operations on models from applications in apps
-
allow_migrate
(db, model)¶ Make sure the auth app only appears in the ‘auth_db’ database.
-
allow_relation
(obj1, obj2, **hints)¶ Allow any relation if a model in apps is involved
-
db_for_read
(model, **hints)¶ Point all operations on apps models to db_name
-
db_for_write
(model, **hints)¶ Point all operations on apps models to db_name
-
cms_local.settings module¶
cms_local.urls module¶
cms_local.wsgi module¶
WSGI config for cms project.
This module contains the WSGI application used by Django’s development server
and any production WSGI deployments. It should expose a module-level variable
named application
. Django’s runserver
and runfcgi
commands discover
this application via the WSGI_APPLICATION
setting.
Usually you will have the standard Django WSGI application here, but it also might make sense to replace the whole Django WSGI application with a custom one that later delegates to the Django one. For example, you could introduce WSGI middleware here, or combine a Django application with an application of another framework.