Right now the recipe only knows the setting wsgi, which can be on or off, and which will create and use a default waitress-based configuration in the respective parts' etc folder.
I propose extending the wsgi option to support having a file path as value in addition to just on/off. Then it would be really easy to support other PasteDeploy-aware WSGI servers without much fuss. In that case it would be the user's responsibility to create the .ini.
Right now the recipe only knows the setting
wsgi, which can be on or off, and which will create and use a defaultwaitress-based configuration in the respective parts'etcfolder.I propose extending the
wsgioption to support having a file path as value in addition to just on/off. Then it would be really easy to support other PasteDeploy-aware WSGI servers without much fuss. In that case it would be the user's responsibility to create the .ini.I'll take a shot at implementing that.