valence/setup.cfg
Lin Yang 48f4c30b21 Use gunicorn instead of werkzeug
Flask use werkzeug as default WSGI container, but it cannot support
production requirement and leads to crash in some cases. So use
gunicorn instead of it.

Change-Id: I2e542ab79c755c2407ae695a6de29c063233269b
Closes-Bug: #1641242
2016-11-11 21:40:51 -08:00

56 lines
1.3 KiB
INI

[metadata]
name = valence
summary = Openstack Valence Project
description-file =
README.rst
author = Intel Corporation
author-email = openstack-dev@lists.openstack.org
home-page = https://launchpad.net/openstack-valence
classifier =
Environment :: OpenStack
Intended Audience :: Information Technology
Intended Audience :: System Administrators
License :: OSI Approved :: Apache Software License
Operating System :: POSIX :: Linux
Programming Language :: Python
Programming Language :: Python :: 2
Programming Language :: Python :: 2.7
Programming Language :: Python :: 3
Programming Language :: Python :: 3.3
Programming Language :: Python :: 3.4
[files]
packages =
valence
[build_sphinx]
source-dir = doc/source
build-dir = doc/build
all_files = 1
[upload_sphinx]
upload-dir = doc/build/html
[compile_catalog]
directory = valence/locale
domain = valence
[update_catalog]
domain = valence
output_dir = valence/locale
input_file = valence/locale/valence.pot
[extract_messages]
keywords = _ gettext ngettext l_ lazy_gettext
mapping_file = babel.cfg
output_file = valence/locale/valence.pot
[build_releasenotes]
all_files = 1
build-dir = releasenotes/build
source-dir = releasenotes/source
[entry_points]
console_scripts =
valence = valence.cmd.api:main