module.exports = {
  images: {
    formats: ['image/avif', 'image/webp'],
    remotePatterns: [
      {
        protocol: 'https',
        hostname: 'res.cloudinary.com',
        port: '',
        pathname: '/YOUR-ACCOUNT/**',
      },
    ],
  },
}

• Dan Schafer - GraphQL at Facebook (efficiency and auth)
• Relay Cursor Connection Specification (pagination)
• Creating a middle-layer (bff)

Modeling Errors in GraphQL (errors)

• https://blog.logrocket.com/handling-graphql-errors-like-a-champ-with-unions-and-interfaces/
• https://engineering.zalando.com/posts/2021/04/modeling-errors-in-graphql.html
• https://itnext.io/the-definitive-guide-to-handling-graphql-errors-e0c58b52b5e1
• https://productionreadygraphql.com/2020-08-01-guide-to-graphql-errors
• https://www.apollographql.com/blog/graphql/error-handling/full-stack-error-handling-with-graphql-apollo/

Implement it yourself

• https://www.apollographql.com/ (javascript)
• https://dev.to/dotnet/learn-how-you-can-use-graphql-in-net-core-and-c-4h96 (c#)
• https://chillicream.com/ (c# - the easy way)
• https://itnext.io/improve-your-graphql-schema-with-the-relay-specification-8952d06998eb
• https://chanind.github.io/2019/05/30/make-your-graphql-api-relay-compatible.html
• https://engineering.zalando.com/posts/2017/02/building-a-relay-compatible-graphql-server.html

Mocking, Stitching, Scalars, Mesh, Inspector, ...

• https://www.graphql-tools.com/

Namespacing

• https://compiledexperience.com/blog/posts/stitched-graphql-rename
• https://github.com/graphql/graphql-spec/issues/163 

Security

• https://auth0.com/blog/build-and-secure-a-graphql-server-with-node-js/
• https://www.apollographql.com/blog/graphql/security/9-ways-to-secure-your-graphql-api-security-checklist/
• https://www.bugcrowd.com/resources/webinars/rest-in-peace-abusing-graphql-to-attack-underlying-infrastructure/

As a service with Hasura

• Mesh to create the ultimate data graph
• On top of existing actor/film database with access control
• Simple ecommerce cart example
• Full stack tutorial

Why Graphql?

• https://42papers.com/p/rest-vs-graphql-a-controlled-experiment
• https://xuorig.medium.com/is-graphql-still-relevant-in-an-http2-world-64964f207b8
• https://medium.com/edge-coders/rest-apis-are-rest-in-peace-apis-long-live-graphql-d412e559d8e4
• https://wundergraph.com/blog/where_in_the_hypecycle_is_graphql_in_2021_analyzing_public_data_from_google_trends_stackoverflow_github_and_hackernews

More

• https://dev.to/peternycander/a-year-of-large-scale-graphql-the-biggest-takeaways-3d5n
• https://blog.devgenius.io/a-principled-approach-to-graphql-query-cost-analysis-8c7243de42c1
• https://tech.okcupid.com/why-we-decided-against-graphql-for-local-state-management/
• https://blog.logrocket.com/graphql-variables-in-simple-terms/
• https://developer.ibm.com/open/projects/openapi-to-graphql/
• https://www.apollographql.com/graph-champions/
• https://wundergraph.com/blog/solving_the_double_quintuple_declaration_problem_in_graphql_applications_how_to_not_repeat_yourself

• kubectl create -f <pod-definition.yaml>
• kubectl apply -f <pod-definition.yaml>
• kubectl delete pod <pod-name>

• kubectl get pods
• kubectl describe pods
• kubectl describe pod <pod-name>
• kubectl port-forward <pod-name> 8080:80
• kubectl exec -it <pod-name> -- bash

Why Kubernetes?

• https://stackoverflow.blog/2021/07/21/why-you-should-build-on-kubernetes-from-day-one/

Why not?

• https://pythonspeed.com/articles/dont-need-kubernetes/

Deployment Strategies

• https://blog.container-solutions.com/kubernetes-deployment-strategies

Templating with Kustomize

• https://blog.stack-labs.com/code/kustomize-101/

Security

• https://media.defense.gov/2021/Aug/03/2002820425/-1/-1/1/CTR_KUBERNETES%20HARDENING%20GUIDANCE.PDF
• https://blog.gitguardian.com/how-to-improve-your-docker-containers-security-cheat-sheet/
• https://github.com/armosec/kubescape

Naming Conventions

• https://stepan.wtf/cloud-naming-convention/Lessons

More

• https://thehftguy.com/2016/11/01/docker-in-production-an-history-of-failure/
• https://blog.gougousis.net/file-permissions-the-painful-side-of-docker/
• https://vsupalov.com/rebuilding-docker-image-development/
• https://marcusnoble.co.uk/2021-09-01-migrating-from-docker-to-podman/

However you might run into 

Unable to connect to the server: dial tcp [::1]:8080: connectex: No connection could be made because the target machine actively refused it.

when trying to run your first 'kubectl create -f some-pod-definition.yaml' command.

And that's just because you forgot to enable it: Setting > Kubernetes > Enable Kubernetes

• Goto certification store: Computer / Local Machine / Remote Desktop
• Remove the current certificate
• net stop SessionEnv
• net start SessionEnv
• Refresh store to check if new certificate is correct

You probably need to check these things:

• Ensure you can connect manually through SQL Server management studio
• Provide connection info to clients by turning on mssql browser service
• Services > SQL Server Browser
• Check Sql Server Network Configuration
• Start > SQL Server Configuration Manager > SQL Server Network Configurations > enable TCP/IP
• On property tab of protocol ensure IP ALL has no dynamics and 1433 as port with 127.0.0.1 enabled
• Restart server instance

• npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules\fsevents)

Warnings for sure are useful during development, but they just overload build servers with noise that should only be there when requested.

You could use npm install --loglevel=error to prevent the warnings to show up in your build logs.

In case you have hard time finding an issue, you could go with npm install --loglevel=silly

(loglevels: silent, error, warn, info, verbose, silly - see also https://docs.npmjs.com/misc/config)

You can correct it with the expression below

var sharedBlacklist = [
  /node_modules[\/\\]react[\/\\]dist[\/\\].*/,
  /website\/node_modules\/.*/,
  /heapCapture\/bundle\.js/,
  /.*\/__tests__\/.*/
];

However, it's more likely that you just downloaded an older react-native example and are trying to run this with a different version than intended.

You could ensure that you install all the package.json dependencies fixed to the version the example was build with.

Or you could upgrade all packages to their latest version and fix any issues that might come from that.

At least with the second option you are ready to go with all the latest tools.

• ELF: Extensible Linking Format is the file format commonly used for Playstation binaries. Eg. BOOT.ELF
• ESR : This is not an abbriviation but a way to load dvd copies. I prefer using network loading with OPL as the whole point is to not only spare your dvd roms but also your playstation laser. Remeber that you need to patch your dvd iso before burning it.
• FMCB : FreeMcBoot allows for booting your playstation into software installed onto your memory card. Which allows you to copy software from a usb-drive. It's kind of catch-22 as to be able to install the initial software on your memory card you need to have a card that has FMCB installed. If you can't buy an initial copy there are tricks to exploit the dvd loading and install it like this, but that's kind of tedious.
• GSM : Graphics Synthetizer Mode Selector you might need to get some specific games working. You can learn about the workings, but it's mostly enough to just lookup the mode in the tables at PS2-home.
• OPL : Open PS2 Loader, far the easiest way to manage playing games over the network. Doesn't work for all games, but use it whenever possible to spare your ps2 laser.
• SMB : Server Message Block aka Samba allows you to setup a network between your PS2 and pc.
• SMS : Simple Media System allows for playing videos. Nice, but not very useful since we all have tablets now.
• MagicGate : Brand of original PS2 memory cards that is needed to run FMCB, watch out as often the bigger ones are fake and will not work. Use an original 8MB for your first experiments.
• uLaunchElf : Your basic file browser that allows you to run executables.

Configuration

Some screenshots of playstation 2 fmcb and opl settings over network.

References

• Playstation 2 - Forum : https://www.ps2-home.com
• SMS - Playstation 2 - Simple Media System Manual
• Game walkthroughs
• Playstation technical architecture
• Setup Playstation 2 Development Environment

• import React from "react"
• use an expression to put comments

{/* you can use this to commend inside your jsx */}

• use a fragment if you want to quickly include an exiting html structure with more then one element at the root

<>
<h1>Some header<h1>
<h2>Some subheader<h2>
</>

• Error: endpoint data missing from graphql config
• ConfigNotFoundError: ".graphqlconfig" file is not available in the provided config directory

To solve this issue, you need to create a .graphqlconfig file in your project root folder.

Tricky part is figuring out what you need to put in there for using Gatsby.

So here is an example:

{
  "name": "Gatsby Schema",
  "schemaPath": "schema.graphql",
  "extensions": {
    "endpoints": {
      "Remote GraphQL Endpoint": {
        "url": "http://localhost:8000/___graphql",
        "headers": {
          "user-agent": "JS GraphQL"
        },
        "introspect": true
      }
    }
  }
}

• npm update

Doing a major update

Ensure you have the 'check updates' module installed, which will give you the ncu command.

npm install -g npm-check-updates

• npm outdated
• ncu -u
• npm update
• npm install

If you keep getting: NCU Real Time Weather is Running......

You installed the module called ncu and will need to uninstall this one first.

npm uninstall ncu -g

npm install -g npm-check-updates -- force

So you basically cancel the test build configuration when the deployment starts.

$buildConfigurationId = '%E2ETestBuildConfigurationId%'
If (![string]::IsNullOrWhitespace($buildConfigurationId)) { 
    Write-Host "Finding test builds"
    $user = '%system.teamcity.auth.userId%'
    $pass = '%system.teamcity.auth.password%'
    $pair = "${user}:${pass}"
    $bytes = [System.Text.Encoding]::ASCII.GetBytes($pair)
    $base64 = [System.Convert]::ToBase64String($bytes)
    $basicAuthValue = "Basic $base64"
    $headers = @{ Authorization = $basicAuthValue; "Content-Type" = "application/xml" }
    $response = Invoke-WebRequest -Uri "http://teamcity.conseur.org/app/rest/builds?locator=buildType:($buildConfigurationId),state:queued" -Method GET -Headers $headers
    $postParams = "<buildCancelRequest comment='Build was canceled because of new deployment.' readdIntoQueue='true' />"
    Foreach($buildId in ([xml]$response.Content).builds.build.id) 
    {
        Write-Host "Cancel queued buildId: $buildId"
        Invoke-WebRequest -Uri "http://teamcity.conseur.org/app/rest/buildQueue/id:$buildId" -Headers $headers -Method POST -Body $postParams
    }
    $response = Invoke-WebRequest -Uri "http://teamcity.conseur.org/app/rest/builds?locator=buildType:($buildConfigurationId),state:running" -Method GET -Headers $headers
    $postParams = "<buildCancelRequest comment='Build was canceled because of new deployment.' readdIntoQueue='false' />"
    Foreach($buildId in ([xml]$response.Content).builds.build.id) 
    {
        Write-Host "Cancel running buildId: $buildId"
        Invoke-WebRequest -Uri "http://teamcity.conseur.org/app/rest/builds/id:$buildId" -Headers $headers -Method POST -Body $postParams
    }
}

windowCustomized = {};
var iframe = document.createElement('iframe');
iframe.onload = function() {
 var standardGlobals = Object.keys(iframe.contentWindow);
 for(var b in window) { 
 const prop = window[b];
 if(window.hasOwnProperty(b) && prop && !prop.toString().includes('native code') && !standardGlobals.includes(b)) {
 windowCustomized[b] = prop;
 }
 }
 //console.info(windowCustomized)
};
iframe.src = 'about:blank';
document.body.appendChild(iframe);
//inspect(windowCustomized);

Control Panel -> Network and Sharing Center -> Change adapter settings -> Press Alt Key to make the Advanced menu visible -> Advanced Settings.

You get this unspecified error when your network adaptor does not include 'Client for Microsoft Networks', which is often forgotten when virtual network adaptors are created automatically.

• Control Panel > Network and Sharing > Change Adaptor settings > Select your current network adaptor > Install > Client > Client for Microsoft Networks > OK > ... > restart or enable/disable network adaptor