Infra
/
lemur
5
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge pull request #249 from kevgliss/master 

Updating docs
This commit is contained in:
kevgliss 2016-02-29 12:51:47 -08:00
parent edba980b56 a30b8b21e4
commit e8f9bc80a0
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/production/index.rst
View File

@ -110,7 +110,7 @@ You can make some adjustments to get a better user experience::
error_log /var/log/nginx/log/lemur.error.log;
location /api {
proxy_pass http://127.0.0.1:5000;
proxy_pass http://127.0.0.1:8000;
proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504;
proxy_redirect off;
proxy_buffering off;
@ -176,7 +176,7 @@ sensitive nature of Lemur and what it controls makes this essential. This is a s
resolver <IP DNS resolver>;
location /api {
proxy_pass http://127.0.0.1:5000;
proxy_pass http://127.0.0.1:8000;
proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504;
proxy_redirect off;
proxy_buffering off;

6
docs/quickstart/index.rst
View File

@ -118,7 +118,7 @@ First, set a password for the postgres user. For this guide, we will use ``lemu
.. code-block:: bash
$ sudo -u postgres psql postgres
$ sudo -u postgres -i
# \password postgres
Enter new password: lemur
Enter it again: lemur
@ -137,7 +137,7 @@ Set a password for lemur user inside Postgres:
.. code-block:: bash
$ sudo -u postgres psql postgres
$ sudo -u postgres -i
\password lemur
Enter new password: lemur
Enter it again: lemur
@ -178,7 +178,7 @@ You'll use the builtin ``HttpProxyModule`` within Nginx to handle proxying. Edi
::
location /api {
proxy_pass http://127.0.0.1:5000;
proxy_pass http://127.0.0.1:8000;
proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504;
proxy_redirect off;
proxy_buffering off;