Package: gunicorn Version: 0.14.5-3+deb7u1 Severity: wishlist Dear Maintainer,
It would be nice to have, like for Apache or many other Debian packages, a "available" / "enabled" configuration system for gunicorn. Instead of loading from /etc/gunicorn.d, the init script could load from /etc/gunicorn/conf-enabled , with files in it being symlinks to real ones in /etc/gunicorn/conf-available . The default example files should then be in /etc/gunicorn/conf-available . Regards, -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages gunicorn depends on: ii python 2.7.3-4 ii python-pkg-resources 0.6.24-1 ii python-setuptools 0.6.24-1 gunicorn recommends no packages. Versions of packages gunicorn suggests: pn python-gevent <none> pn python-pastedeploy <none> pn python-setproctitle <none> pn python-tornado <none> -- Configuration Files: /etc/init.d/gunicorn changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
