conntrackt Files · projtest/projtest/wsgi.py

Files @ 827c719a42ed

Branch filter:

Location: conntrackt/projtest/projtest/wsgi.py

827c719a42ed 1.9 KiB text/x-python Show Annotation Show as Raw Download as Raw

branko

CONNT-28: Updates to documentation, requirements handling, and minor fixes:

- Fixed syntax error in MANIFEST.in file for recursive-exclude.
- Merged the about section from documentation into the README file.
Documentation now references README file instead of duplicating the
data. Minor formatting and wording fixes were made as well.
- Updated Sphinx configuration to use same string for both release and
version (deduplicate it a bit).
- Added a new, develoment-related, section to the documentation. Describes
how to set-up the development environment, as well as some maintenance
tasks.
- Updated quickstart instructions so they actually work. Switched to
using the pip install from PyPI instead of repository.
- Introduced pip-tools use for the development requirements file.
- Switched to using more fixed requirements in the setup.py.
- Removed test requirements from the setup.py.

# -*- coding: utf-8 -*-
#
# Copyright (C) 2013 Branko Majic
#
# This file is part of Django Conntrackt.
#
# Django Conntrackt is free software: you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by the Free
# Software Foundation, either version 3 of the License, or (at your option) any
# later version.
#
# Django Conntrackt is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
# FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
# details.
#
# You should have received a copy of the GNU General Public License along with
# Django Conntrackt.  If not, see <http://www.gnu.org/licenses/>.
#


"""
WSGI config for projtest 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.

"""
import os

os.environ.setdefault("DJANGO_SETTINGS_MODULE", "projtest.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
application = get_wsgi_application()

# Apply WSGI middleware here.
# from helloworld.wsgi import HelloWorldApplication
# application = HelloWorldApplication(application)