> On 24 Jul 2018, at 8:42 am, YKdvd <[email protected]> wrote: > > Yes, just checked, and surrounding those two values with single quotes in the > generated httpd.conf works as well in my "domain users" group case. This > case is probably limited to those using PAM/AD for login authentication on > linux boxes, but if those single quotes don't have any other side effects, it > might be nice if this edge case worked out of the box.
Okay, will commit change. > It looks like there is no way to set the "display-name" of the generated > WSGIDaemonProcess from setup-server? It looks like you use a "daemon_name" > option you build from host/port/uid, and it doesn't have a command-line > override capability? Correct, never saw a need to have it be able to be overridden for mod_wsgi-express. I just set it to reasonable default. What is the use case? > Similarly with WSGIPythonHome, you set it to "python_home" option which is > set to "sys.prefix". So it will pick up whatever virtual environment is > active when mod_wsgi-express is run, but can't be specified on the command > line? I can tweak these things in the generated config, but I was just > curious. Why would you need to override it? It works that way because if have an option, people will immediately start trying to set it and likely break things. You should always install mod_wsgi-express into the virtual environment you want to use, not system Python. Graham -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
