Hello Chris! Tue, 9 Jul 2013 14:56:17 +0100, you wrote:
> Gael Le Mignot wrote: >> It would be nice to have, like for Apache or many other Debian >> packages, a "available" / "enabled" configuration system for >> gunicorn. > Can you think of usecases where this would be useful? > As it is unlikely that official Debian packages will be shipping with > gunicorn worker configurations, the ability to have configs "available" > but not enabled does not seem particularly useful. Yes, of course, it wasn't for the default configurations; it's more like with Apache, on our production or pre-production servers, we sometimes have to temporarily disable a site. We can do it by moving the file to another place than /etc/gunicorn.d but having the same kind of system than Apache (between /etc/apache2/sites-available and /etc/apache2/sites-enabled) would be convenient. It can also be used to have centralised "available" configuration when deploying on a cluster, even the "enabled" configurations aren't the same of each node (like, some configurations are only enabled in case of failure on one node). More generally, we use gunicorn with Apache, and having the enable/available in one and not with the other is a bit frustrating, but it is indeed a very low-priority request. Regards, -- Gaël Le Mignot - [email protected] Pilot Systems - 82, rue de Pixérécourt - 75020 Paris Tel : +33 1 44 53 05 55 - www.pilot-systems.net Gérez vos contacts et vos newsletters : www.cockpit-mailing.com -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
