I have successfully set up a web application on production server using mod_wsgi-express and slowly learning, with hit and trial, how to make the command (and arguments) to start the server, more useful and efficient. This is what I have so far and would be happy to get feedback on:
nohup mod_wsgi-express start-server --application-type module mysitename.wsgi --server-root /etc/mod_wsgi-80 --reload-on-changes & I ssh into a Google Compute Engine which disconnects after sometime (also terminating all processes started during that session) so using nohup and using '&' at the end so it runs as a background process. Using server-root so as not to rely on the tmp directory. (Also, hope using reload-on-changes here is ok (in the examples I saw it being used mostly with runmodwsgi). If I ever need to stop the server, I find the process (ps -ef | grep mod_wsgi) and kill it. There are a number of processes that come up and killing the first one kills the others too. thanks, Anupam -- 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.
