| /* | |
| * This is bad -- it will not "hot reload" with changes | |
| * and leads to confusing bugs | |
| */ | |
| exports.createPages = async function createPages({ actions, graphql }) { | |
| const { data } = await graphql(` | |
| { | |
| allMarkdownRemark { | |
| nodes { | |
| frontmatter { |
SHIFT at boot to enter recovery modemount -o rw,remount /etc/network/interfaces with correct gateway(Note also, consider adding DHCP to /etc/network/interfaces) to test and then reset /etc/network/interfaces
iface ens160 inet dhcp
| /* | |
| * you will probably also want to do something like gatsby-remark-autolink-headers | |
| * https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-remark-autolink-headers/src/gatsby-ssr.js | |
| */ |
| import React from "react" | |
| export default function IFrame({ src, height, title, width, ...rest }) { | |
| return ( | |
| <div | |
| className={`gatsby-resp-iframe-wrapper`} | |
| css={{ | |
| paddingBottom: `${(height / width) * 100}%`, | |
| position: `relative`, | |
| height: 0, |
| exports.sourceNodes = async function sourceNodes({ actions, webhookBody }) { | |
| /* | |
| * Note: this is the webhook body that is passed from | |
| * your CMS -> Gatsby Preview -> this function | |
| * It will be a JS object, and you can use this data to "get consistent" | |
| * with the remote CMS state | |
| * Note: if you have a structure for deletes/creates/updates use it here! | |
| */ | |
| if (webhookBody && webhookBody.updates) { | |
| await Promise.all( |
| async function getAllUsers() { | |
| const delay = duration => new Promise(resolve => setTimeout(resolve, duration)) | |
| const items = Array.from(document.querySelector('.friends-container').querySelectorAll('li')) | |
| let emails = [] | |
| for (let el of items) { | |
| if (el && el.querySelector('.edit-btn')) { | |
| el.querySelector('.edit-btn').click() | |
| await delay(1000) | |
| require("dotenv").config({ | |
| path: `.env.${process.env.NODE_ENV}` | |
| }) | |
| const path = require("path") | |
| const createPaginatedPages = require("gatsby-paginate") | |
| const cloudinary = require("cloudinary").v2 | |
| cloudinary.config({ | |
| cloud_name: `${process.env.CLOUDINARY_NAME}`, |
| const execa = require('execa') | |
| exports.onPreBootstrap = () => { | |
| return execa('npm', ['run', 'compile']) | |
| } |
| import React from "react" | |
| import { Link, graphql } from "gatsby" | |
| import Layout from "../components/layout" | |
| import Image from "../components/image" | |
| import SEO from "../components/seo" | |
| const withAuthentication = Page => { | |
| return class extends React.Component { | |
| state = { |
| title |
|---|
Gatsby and GraphQL: Sitting in a Tree K-I-S-S-I-N-G |
Gatsby uses GraphQL — although it does not require it. In this talk, I go into the technical reasons of why gatsby uses graphql and why that is so appealing. I’ll deep dive into the innards of Gatsby to show what tools and libraries we use to make this schema as extensible and useful as possible, and reveal our vision for the future for how we envision Gatsby’s usage of GraphQL evolving. At the end, I’ll do some live coding to show how we can extend this internal schema with any data source and query it at build time (optional).