mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-22 06:51:32 +03:00
76ceb707f4
This PR builds console static assets into the server docker image at `/srv/console-assets`. When env var `HASURA_GRAPHQL_CONSOLE_ASSETS_DIR=/srv/console-assets` or flag `--console-assets-dir=/srv/console-assets` is set on the server, the files in this directory are served at `/console/assets/*`.
The console html template will have a variable called `cdnAssets: false` when this flag is set and it loads assets from server itself instead of CDN.
The assets are moved to a new bucket with a new naming scheme:
```
graphql-engine-cdn.hasura.io/console/assets/
/common/{}
/versioned/<version/{}
/channel/<channel>/<version>/{}
```
Console served by CLI will still load assets from CDN - will fix that in the next release.
31 lines
667 B
ReStructuredText
31 lines
667 B
ReStructuredText
GraphQL engine server configuration
|
|
===================================
|
|
|
|
.. contents:: Table of contents
|
|
:backlinks: none
|
|
:depth: 1
|
|
:local:
|
|
|
|
Hasura supports various flags and options for customising how you are running the GraphQL engine in your environment.
|
|
|
|
Server flags
|
|
------------
|
|
|
|
See the :doc:`server flag reference <reference>` for all the available flags.
|
|
|
|
Use cases
|
|
---------
|
|
|
|
The following are a few configuration use cases:
|
|
|
|
- :ref:`add-admin-secret`
|
|
- :ref:`cli-with-admin-secret`
|
|
- :ref:`configure-cors`
|
|
- :ref:`console-assets-on-server`
|
|
|
|
.. toctree::
|
|
:hidden:
|
|
|
|
Server flags reference <reference>
|
|
Server config examples <config-examples>
|