hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-15 17:31:56 +03:00
Code Issues Projects Releases Wiki Activity
63ad2c4fc5
graphql-engine/server/src-rsr/console.html

102 lines
3.1 KiB
HTML
Raw Normal View History

server: console is served at /console Closes #16 (#22)
2018-06-29 14:05:09 +03:00
<html lang="en-us">
<head>
<script>
window.__env = {
update console variables and contributing guide (close #517) (#538) Changes `consoleMode` variable templated by HGE to `server` and modified console to respect in the same way and adds a patch to continue working with the older HGEs - [x] Server - [x] Console
2018-09-27 14:40:32 +03:00
consoleMode: "server",
indicate access key is set in the console context (close #426) (#447)
2018-09-14 16:27:46 +03:00
urlPrefix: "/console",
add consolePath in console.html template (#1222) Server templates `consolePath` key in `window.__env` object in console html template. If server is hit at `/console/table/author` then `window.__env` in served html looks like ``` {   consoleMode: "server",   urlPrefix: "/console",   consolePath: "/console/table/author",   isAccessKeySet: true } ```
2018-12-18 12:39:01 +03:00
consolePath: "{{consolePath}}",
rename access-key to admin-secret (close #1347) (#1540) Rename the admin secret key header used to access GraphQL engine from X-Hasura-Access-Key to X-Hasura-Admin-Secret. Server CLI and console all support the older flag but marks it as deprecated.
2019-02-14 12:37:47 +03:00
isAccessKeySet: {{isAdminSecretSet}},
isAdminSecretSet: {{isAdminSecretSet}},
bundle console assets into server (close #516, close #521, close #2130) (#2192) 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.
2019-05-16 10:45:29 +03:00
enableTelemetry: {{enableTelemetry}},
assetsPath: "https://graphql-engine-cdn.hasura.io/console/assets",
assetsVersion: "{{assetsVersion}}",
cdnAssets: {{cdnAssets}},
server: console is served at /console Closes #16 (#22)
2018-06-29 14:05:09 +03:00
};
bundle console assets into server (close #516, close #521, close #2130) (#2192) 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.
2019-05-16 10:45:29 +03:00
window.__env.versionedAssetsPath = window.__env.assetsPath;
server: console is served at /console Closes #16 (#22)
2018-06-29 14:05:09 +03:00
</script>
</head>
<body>
<style>
.mainContent {
display: 'none';
opacity: 0;
transition: opacity .20s linear;
}
.mainContent.show {
display: 'block';
opacity: 1;
transition: opacity .20s linear;
}
</style>
<div id="loading">
<div class="page-loading" style="
min-height: 100vh;
width: 100%;
display: flex;
align-items: center;
font-family: sans-serif;
justify-content: center;
">
<span class="" style="
font-size: 2em;
margin-top: -3em;
color: #848484;
">
Loading...
</span>
</div>
</div>
<div id="content" class="mainContent"></div>
bundle console assets into server (close #516, close #521, close #2130) (#2192) 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.
2019-05-16 10:45:29 +03:00
<script>
change default endpoint to v1/graphql; remove semver checks (#2181)
2019-05-16 12:08:44 +03:00
// helper functions
bundle console assets into server (close #516, close #521, close #2130) (#2192) 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.
2019-05-16 10:45:29 +03:00
const loadIcon = (url) => {
linkElem = document.createElement('link');
linkElem.rel = 'icon';
update console favicons to png (#2287)
2019-05-29 07:33:29 +03:00
linkElem.type = 'image/png';
bundle console assets into server (close #516, close #521, close #2130) (#2192) 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.
2019-05-16 10:45:29 +03:00
linkElem.href = url;
document.head.append(linkElem);
};
const loadCSS = (url) => {
linkElem = document.createElement('link');
linkElem.rel = 'stylesheet';
linkElem.charset = 'UTF-8';
linkElem.href = url;
document.body.append(linkElem);
};
const loadScript = (url) => {
scriptElem = document.createElement('script');
scriptElem.charset = 'UTF-8';
scriptElem.src = url;
document.body.append(scriptElem);
};
const prependSlash = (str) => str === '' ? '' : '/' + str;
change default endpoint to v1/graphql; remove semver checks (#2181)
2019-05-16 12:08:44 +03:00
const loadAssets = () => {
bundle console assets into server (close #516, close #521, close #2130) (#2192) 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.
2019-05-16 10:45:29 +03:00
loadCSS(window.__env.assetsPath + '/common/css/font-awesome.min.css.gz');
update console favicons to png (#2287)
2019-05-29 07:33:29 +03:00
loadIcon(window.__env.assetsPath + '/common/img/favicon_green.png');
bundle console assets into server (close #516, close #521, close #2130) (#2192) 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.
2019-05-16 10:45:29 +03:00
loadCSS(window.__env.versionedAssetsPath + '/main.css.gz');
loadScript(window.__env.versionedAssetsPath + '/main.js.gz');
loadScript(window.__env.versionedAssetsPath + '/vendor.js.gz');
change default endpoint to v1/graphql; remove semver checks (#2181)
2019-05-16 12:08:44 +03:00
};
bundle console assets into server (close #516, close #521, close #2130) (#2192) 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.
2019-05-16 10:45:29 +03:00
// if cdnAssets is set to false, load assets from server instead of cdn
if (window.__env.cdnAssets === false) {
window.__env.assetsPath =
window.location.pathname.slice(
0, window.location.pathname.lastIndexOf(window.__env.consolePath)
) + '/console/assets';
// set the path to get versioned assets from server
window.__env.versionedAssetsPath = window.__env.assetsPath + '/versioned';
// otherwise load from cdn itself
} else {
// set the path (cdn-based) to get assets from
window.__env.versionedAssetsPath = window.__env.assetsPath + prependSlash(window.__env.assetsVersion);
}
change default endpoint to v1/graphql; remove semver checks (#2181)
2019-05-16 12:08:44 +03:00
// load the assets now
loadAssets();
bundle console assets into server (close #516, close #521, close #2130) (#2192) 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.
2019-05-16 10:45:29 +03:00
</script>
server: console is served at /console Closes #16 (#22)
2018-06-29 14:05:09 +03:00
</body>
indicate access key is set in the console context (close #426) (#447)
2018-09-14 16:27:46 +03:00
</html>
Reference in New Issue Copy Permalink