Docs: Updates for SE team

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/10902
GitOrigin-RevId: 4093ac7fec9338fdd1d7269e7b85f8d27f43f2a5
This commit is contained in:
Rob Dominguez 2024-06-24 10:05:36 -05:00 committed by hasura-bot
parent 1378730d43
commit f8187ab76d
2 changed files with 10 additions and 4 deletions

View File

@ -95,6 +95,13 @@ database's driver's documentation.
:::
:::info Running MySQL locally?
If so, remember that your database will only be accessible to the outside internet if you tunnel your connection using a
service like [ngrok](https://ngrok.com).
:::
### Step 3: Track tables and run GraphQL API queries
Now that you have successfully connected your MySQL database to Hasura, you can track tables and use Hasura to

View File

@ -49,9 +49,8 @@ database nodes too. Currently, read-replica connections use one setting for all
specific values for each node. Therefore, you need to be aware of the total number of connections when scaling Hasura to
multiple nodes.
With Read replicas, Hasura can route queries and subscriptions to multiple
databases. However, you will need to balance connections between database nodes
too.
With Read replicas, Hasura can route queries and subscriptions to multiple databases. However, you will need to balance
connections between database nodes too.
#### `HASURA_GRAPHQL_LIVE_QUERIES_MULTIPLEXED_REFETCH_INTERVAL`
@ -110,7 +109,7 @@ Observability tools help us track issues, alert us to errors, and allow us to mo
is critical in production. There are many open-source and commercial services. However, you may have to combine many
tools because of the architectural complexity. For more information, check out our
[observability section](/observability/overview.mdx) and our
[observability best practives](/observability/observability-best-practices.mdx).
[observability best practices](/observability/observability-best-practices.mdx).
## Software architecture and best practices