git clone --depth 1 https://github.com/hlissner/doom-emacs ~/.emacs.d
cd ~/.emacs.d
bin/doom install
Optional
{-# LANGUAGE FlexibleContexts #-} | |
module Main where | |
import Control.Applicative (liftA2) | |
import Control.Monad.Reader (MonadIO, MonadReader, ReaderT, ask, | |
runReaderT) | |
{- | Let's say we have a deeply nested call stack. There are many functions | |
calling other functions. |
#!/bin/bash | |
set -e | |
resolution="$1" | |
if [[ -z "$resolution" ]]; then | |
resolution="1366x768" | |
echo "[WARN] No resolution passed. Defaulting to $resolution." | |
fi | |
outfile="$2" |
/* The error handling library */ | |
type ResultError<E> = { | |
errors: E, | |
trace?: any | |
} | |
type Success<T> = { | |
value: T | |
} |
program: badblocks
sudo badblocks -v /dev/sdxy > badsectors.txt
This guide helps you to setup the image registry configuration on a multi-node Hasura installation on GKE.
This is required in multi-node setups, because the sshd agent (which builds the docker images on git push) needs to push the image to an external image registry service, so that the image is available on all the nodes.
curl 'http://localhost:8080/v1alpha1/graphql' -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0' -H 'Accept: */*' -H 'Accept-Language: en-US,en;q=0.5' --compressed -H 'Referer: http://localhost:8080/console/api-explorer' -H 'content-type: application/json' -H 'x-hasura-role: admin' -H 'Origin: http://localhost:8080' -H 'DNT: 1' -H 'Connection: keep-alive' --data '{"query":"\n query IntrospectionQuery {\n __schema {\n queryType { name }\n mutationType { name }\n subscriptionType { name }\n types {\n ...FullType\n }\n directives {\n name\n description\n locations\n args {\n ...InputValue\n }\n }\n }\n }\n\n fragment FullType on __Type {\n kind\n name\n description\n fields(includeDeprecated: true) {\n name\n description\n args {\n ...InputValue\n }\n type {\n ...TypeRef\n |
If you are trying to install Hasura on a multi-node Kubernetes cluster and wondering how to setup the image registry, this is the guide for you.
Let us see how to setup a private image registry on a multi-node Hasura k8s platform cluster. This is required in multi-node setups, because the sshd agent (which builds the docker images on git push) needs to push the image to an external image registry service, so that the image is available on all the nodes.
NOTE: Do these steps before installing Hasura on the Kuberentes cluster.
import random | |
from datetime import datetime | |
import time | |
import json | |
import requests | |
query = """ | |
mutation { | |
insert_conditions (objects: [ | |
{ |
version: '2' | |
services: | |
timescale: | |
image: timescale/timescaledb:latest-pg10 | |
restart: always | |
environment: | |
POSTGRES_PASSWORD: postgrespassword | |
volumes: | |
- db_data:/var/lib/postgresql/data | |
graphql-engine: |