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.
"""
import os
# We defer to a DJANGO_SETTINGS_MODULE already in the environment. This breaks
# if running multiple sites in the same mod_wsgi process. To fix this, use
# mod_wsgi daemon mode with each site in its own daemon process, or use
# os.environ["DJANGO_SETTINGS_MODULE"] = "kindy.settings"
#os.environ.setdefault("DJANGO_SETTINGS_MODULE", "kindy.settings")
# This application object is used by any WSGI server configured to use this
# file. This includes Django's development server, if the WSGI_APPLICATION
# setting points here.
from django.core.wsgi import get_wsgi_application
from utils.deployment import get_dj_env
'''preverimo ali app tece lokalno ali na heroku
na Heroku smo nastavili: heroku config:add DJANGO_DEV_ENV=1 (prod) ali 2 (dev).
'''
if get_dj_env() == 'local':
os.environ.setdefault("DJANGO_SETTINGS_MODULE", 'kindy.settings.local')
application = get_wsgi_application()
else:
from dj_static import Cling
application = Cling(get_wsgi_application())
from utils.deployment import get_dj_env
DJ_ENV = get_dj_env()
if DJ_ENV == "local":
from local import *
elif DJ_ENV == "prod":
from prod import *
elif DJ_ENV == "dev":
from dev import *
