Skip to content

Files

Latest commit

 

History

History

step11_dotenv

We want to keep envirnoment variables seprate in a .env file, and not commiting in repo

npm i dotenv --save

Create a ".env" file at the root and define the following two envirnoment variables

CONTENTFUL_SPACE_ID=your_space_id_grab_it_from_contentful

CONTENTFUL_ACCESS_TOKEN=your_token_id_grab_it_from_contentful

require and config dotenv package in gatsby-config.js file

gatsby develop

You can view the GraphQL Explorer at:

http://localhost:8000/___graphql

select the allContentfulBlogPost/edges/node in the GraphQL Explorer and create the Query and run it to test it.

Update index.tsx

You can now view the website with Contentful blog post title content in the browser. ⠀ http://localhost:8000/

Before commiting your code to git add .env in .gitignore

Gatsby

Minimal starter for installing recipes

Note that this starter does not include any pages by default.

This starter is meant as a minimal reproduction of a Gatsby project in order to facilitate recipe installation.

🚀 Quick start

  1. Create a Gatsby site.

    Use the Gatsby CLI to create a new site, specifying the minimal starter.

    # create a new Gatsby site using the minimal starter
    gatsby new my-site https://github.com/gatsbyjs/gatsby-starter-minimal
  2. Start developing.

    Navigate into your new site’s directory and start it up.

    cd my-site/
    gatsby develop
  3. Open the code and start customizing!

    Your site is now running at http://localhost:8000!