mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-14 17:02:49 +03:00
Docs: Refactor UPPERCASE admonitions
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/8717 GitOrigin-RevId: 1bd5c2dff9fe19f5d2bc3fec674c1d77f7d53861
This commit is contained in:
parent
69949eff60
commit
7053b87616
@ -90,7 +90,7 @@ warning header:
|
||||
Warning: 199 - cache-store-capacity-exceeded
|
||||
```
|
||||
|
||||
:::info SLIDING WINDOW POLICIES
|
||||
:::info Sliding window policies
|
||||
|
||||
A sliding window policy maintains a queue of a specified size, into which entities flow. When the queue is full and a
|
||||
new entity arrives, the oldest entity in the queue is removed from the window (FIFO).
|
||||
|
@ -61,7 +61,7 @@ query MyProducts @cached(ttl: 120) {
|
||||
the cached directive"
|
||||
/>
|
||||
|
||||
:::tip DEFAULT TTL
|
||||
:::tip Default TTL
|
||||
|
||||
By default the TTL is set to 60 seconds.
|
||||
|
||||
|
@ -80,7 +80,7 @@ If you're using Hasura Cloud, you can quickly find your IP address from the
|
||||
|
||||
<Thumbnail src="/img/projects/hasura-cloud-ip.png" alt="Hasura Cloud IP field" />
|
||||
|
||||
:::info SELF-HOSTED INSTANCES
|
||||
:::info Self-hosted instances
|
||||
|
||||
If you're using a self-hosted solution, you'll need to determine the IP address
|
||||
manually depending on your hosting service.
|
||||
@ -98,14 +98,14 @@ this server`, if you require intra-Azure connectivity.
|
||||
|
||||
Finally, click `Review + create` to review your settings, and if you're happy, create the database.
|
||||
|
||||
:::info POSTGRES PERMISSIONS
|
||||
:::info Postgres permissions
|
||||
|
||||
If you're using a database user other than the default one, make sure to give it the right
|
||||
[Postgres permissions](/deployment/postgres-requirements.mdx#managed-pg-permissions).
|
||||
|
||||
:::
|
||||
|
||||
:::info JIT COMPATIBIILITY
|
||||
:::info JIT compatibility
|
||||
|
||||
For Azure flexible server, Hasura `v1.x` does not work with
|
||||
[JIT](https://www.postgresql.org/docs/11/runtime-config-query.html#GUC-JIT) turned on. JIT can be turned off from Azure
|
||||
|
@ -48,7 +48,7 @@ The file structure of the project directory containing the Metadata, Migration,
|
||||
Once the project directory is created with the application assets, push them to a public GitHub repository to be used as
|
||||
the source of your One Click Deploy app.
|
||||
|
||||
:::info LOOKING FOR AN EXAMPLE?
|
||||
:::info Looking for an example?
|
||||
|
||||
Check out what a Hasura project directory looks like with this
|
||||
[e-commerce app](https://github.com/hasura/data-hub/tree/main/data-models/postgres/ecommerce/hasura).
|
||||
|
@ -20,7 +20,7 @@ One Click Deploy to Hasura Cloud enables you to instantly deploy a Hasura applic
|
||||
Hasura Cloud. This feature can be used to share Hasura applications with Metadata, Migrations and Seeds with anyone and
|
||||
they can try them out instantly on Hasura Cloud.
|
||||
|
||||
:::info TRY IT OUT
|
||||
:::info Try it out
|
||||
|
||||
- Try deploying some sample apps from the [Hasura Hub](https://hasura.io/hub/).
|
||||
- [Create a One Click Deploy app](./create-one-click-to-deploy-apps.mdx) to share your Hasura application.
|
||||
|
Loading…
Reference in New Issue
Block a user