Skip to content

Commit

Permalink
Update install.rst
Browse files Browse the repository at this point in the history
Clarified section on running GHC under a sub-path after @justb4's comments
  • Loading branch information
archaeogeek committed Oct 11, 2018
1 parent 339d3fe commit f00eb43
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/install.rst
Expand Up @@ -131,10 +131,10 @@ Start using the built-in ``mod_wsgi`` server:
To enable in Apache, use ``GeoHealthCheck.wsgi`` and configure in Apache To enable in Apache, use ``GeoHealthCheck.wsgi`` and configure in Apache
as per the main Flask documentation. as per the main Flask documentation.


Running under a sub-directory Running under a sub-path
----------------------------- -----------------------------


By default GeoHealthCheck is configured to run under the root directory on the webserver. However, it can be configured to run under a sub-directory. The method for doing this depends on the webserver you are using. By default GeoHealthCheck is configured to run under the root directory on the webserver. However, it can be configured to run under a sub-path. The method for doing this depends on the webserver you are using, but the general requirement is to pass Flask's ``SCRIPT_NAME`` environment variable when GeoHealthCheck is started.


Below is an example of how to use nginx and gunicorn to run GeoHealthCheck in a directory "geohealthcheck", assuming that you have nginx and gunicorn already set up and configured: Below is an example of how to use nginx and gunicorn to run GeoHealthCheck in a directory "geohealthcheck", assuming that you have nginx and gunicorn already set up and configured:


Expand Down

0 comments on commit f00eb43

Please sign in to comment.