fix docs content (#1603)

This commit is contained in:
Rikin Kachhia 2019-02-14 16:44:25 +05:30 committed by GitHub
parent 12ecea16d0
commit c90b03dbc7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 6 additions and 6 deletions

View File

@ -26,4 +26,4 @@ Run the docker command with an admin-secret env var
.. note::
If you're looking at adding access control rules for your data to your GraphQL API then head
to :doc:`Authentication / access control <../auth/index>`.
to :doc:`Authentication / access control <../../auth/index>`.

View File

@ -70,9 +70,9 @@ For ``serve`` sub-command these are the flags and ENV variables available:
- ``HASURA_GRAPHQL_ENABLE_CONSOLE``
- Enable the Hasura Console (served by the server on ``/`` and ``/console``)
* - ``--access-key <SECRET_ACCESS_KEY>``
- ``HASURA_GRAPHQL_ACCESS_KEY``
- Secret access key, for admin access to this instance. This is mandatory
* - ``--admin-secret <ADMIN_SECRET_KEY>``
- ``HASURA_GRAPHQL_ADMIN_SECRET``
- Admin secret key, required to access this instance. This is mandatory
when you use webhook or JWT.
* - ``--auth-hook <WEBHOOK_URL>``

View File

@ -36,4 +36,4 @@ In case you're using the CLI to open the Hasura console, use the ``admin-secret`
.. note::
If you're looking at adding access control rules for your data to your GraphQL API then head
to :doc:`Authentication / access control <../auth/index>`.
to :doc:`Authentication / access control <../../auth/index>`.

View File

@ -49,4 +49,4 @@ In case you're using the CLI to open the Hasura console, use the ``admin-secret`
.. note::
If you're looking at adding access control rules for your data to your GraphQL API then head
to :doc:`Authentication / access control <../auth/index>`.
to :doc:`Authentication / access control <../../auth/index>`.