So, what are the chances that the Apache requirement can be removed/laxed in leu of any other web server? Especially since its a fallback system and if one tries to install nav on a machine that already has NGINX on it, it downright fails. Hardcore.
----- Justin Partain Cell: (214) 923-9252 Email: jpartain89@gmail.com
Sent with Airmail on OS X
On 11. des. 2016 03:36, Justin Partain wrote:
So, what are the chances that the Apache requirement can be removed/laxed in leu of any other web server? Especially since its a fallback system and if one tries to install nav on a machine that already has NGINX on it, it downright fails. Hardcore.
As far as I know that should definitely be doable, but I'll let our main guy answer that. He'll be back next week.
On Sat, 10 Dec 2016 20:36:07 -0600 Justin Partain jpartain89@gmail.com wrote:
So, what are the chances that the Apache requirement can be removed/laxed in leu of any other web server? Especially since its a fallback system and if one tries to install nav on a machine that already has NGINX on it, it downright fails. Hardcore.
Probably not a problem - we do not actually run NAV under Apache/mod_wsgi in our production environment, we use uwsgi.
However, the Debian package currently only provides example config for Apache/mod_wsgi, and an option for automatic restart of Apache2 on NAV upgrades. We need to have proper alternatives and doc before we can remove the requirement outright.
Let me suggest you report a feature request at https://bitbucket.org/mbrekkevold/nav-debian/issues
-
John Magne Bredal -
Justin Partain -
Morten Brekkevold