hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-09-21 07:28:26 +03:00
Code Issues Projects Releases Wiki Activity

docs: change "Step 0" to "Before you begin" (close #5335) (#5348)

Browse Source
This commit is contained in:
sezgi 2020-07-14 14:30:35 -07:00 committed by GitHub
parent 24592a516b
commit a96e248a0c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 12 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/graphql/manual/migrations/config-v1/manage-migrations.rst
View File

@ -31,8 +31,8 @@ Let's say we have the following two tables in our schema:
Now we want to set up migrations starting with this schema.
Step 0: Disable the console on the server
-----------------------------------------
Before you begin
----------------
To use migrations effectively, the console on the server (which is served at
``/console``) should be disabled and all changes must go through the console

4
docs/graphql/manual/migrations/migrations-setup.rst
View File

@ -30,8 +30,8 @@ Let's say we have the following two tables in our schema:
Now we want to set up migrations starting with this schema.
Step 0: Disable console on the server
-------------------------------------
Before you begin
----------------
To use migrations effectively, the console on the server (which is served at ``/console``) should be
disabled and all changes must go through the console served by the CLI. Otherwise, changes could be

7
docs/graphql/manual/migrations/upgrade-v2.rst
View File

@ -43,11 +43,10 @@ For example,
Upgrade steps
-------------
Step 0: Take a backup
^^^^^^^^^^^^^^^^^^^^^
Before you begin
^^^^^^^^^^^^^^^^
It is recommended that you take a backup of your Hasura project before attempting
to upgrade to ``config v2``
Make sure you take a backup of your Hasura project before upgrading to ``config v2``.
Step 1: Upgrade to the latest CLI
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

6
docs/graphql/manual/schema/remote-relationships/action-relationships.rst
View File

@ -21,10 +21,10 @@ Introduction
Create an action relationship
-----------------------------
Step 0: Create an action
^^^^^^^^^^^^^^^^^^^^^^^^
Before you begin
^^^^^^^^^^^^^^^^
First, create an action, either :ref:`from scratch <create_actions>` or :ref:`derive it from an existing mutation <derive_actions>`.
Create an action either :ref:`from scratch <create_actions>` or :ref:`derived from an existing mutation <derive_actions>`.
Step 1: Open the action relationship section
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

4
docs/graphql/manual/schema/remote-relationships/remote-schema-relationships.rst
View File

@ -32,8 +32,8 @@ Because Hasura is meant to be a GraphQL server that you can expose directly to y
Create remote schema relationships
----------------------------------
Step 0: Add a remote schema
^^^^^^^^^^^^^^^^^^^^^^^^^^^
Before you begin
^^^^^^^^^^^^^^^^
Add a remote schema as described :ref:`here <adding_schema>`.