Cosmic JS is a headless CMS that content editors can use to edit and publish content. Gatsby Cloud allows you to integrate your site with Cosmic JS in order to run performant builds and preview content changes made in the CMS before publishing.
Sign in with GitHub. You’ll be asked to authorize the Gatsby Cloud app with your GitHub account. If you need to request access to one or more repositories, you can click “request access” here or later, when creating an instance.
Once signed in, configuring Gatsby Cloud with Cosmic JS requires several steps that are walked through below.
Once you’ve authenticated with Cloud and GitHub, you can create an instance from the “Create a new Gatsby Cloud site” page.
Use the “I already have a Gatsby site” flow to manually integrate your site.
Pick your Gatsby site from the list of GitHub repositories. You can use the search input to narrow down the list.
If you don’t see your site, it might be because it belongs to a GitHub organization, rather than your personal account. You can connect a new GitHub Organization.
Note: Repositories must contain one Gatsby project configured at their root to be enabled. Gatsby Cloud works best with Gatsby version 2.19.25 and higher.
You’ll need to select a branch and then indicate the publish directory where the
gatsby-config.js lives. If you leave the field blank, it defaults to the root of the site.
Once the branch and base directory are correct, select “Next.”
If you have already configured an instance of Cosmic JS or if you don’t see Cosmic JS in the “Automatic Provisioning” list, skip to Manual Integration.
If you do see Cosmic JS in the “Automatic Integrations” section, consider using the “Automatic Integration” flow and Gatsby Cloud will set-up your CMS for you!
Find Cosmic JS in the automatic integrations section, press “Connect” and follow the set-up instructions to link Cosmic JS with Gatsby Cloud.
As an example, consider the following screenshot using Contentful:
Once you’ve authorized Cosmic JS and selected the appropriate organization, press “Create site” which will create your instance.
First, click “Skip this step” to configure Cosmic JS manually.
Gatsby Cloud will automatically try and detect environment variables necessary in your
gatsby-config.js. However — consider adding any additional variables that automatic detection may have missed. See “Setting up Environment Variables” for more info.
Note that you will be able to add, delete, or update these later on in “Site Settings”.
Once you’ve added the necessary environment variables, you can press “Create site” which will create your instance in Gatsby Cloud!
After following the “Automatic Integration” or “Manual Integration” flow you now have an instance of Gatsby Cloud configured with environment variables and a provided Gatsby Preview instance you can share with your team. Woo-hoo!
Cosmic JS uses a webhook to inform Gatsby Cloud when content changes. Gatsby Cloud will automatically add webhooks to push content changes to your preview instance. Additionally, publishing content will trigger a new build!
You can view webhooks set up for your Cosmic JS bucket in your bucket’s settings section. If you do not see any webhooks listed with an endpoint from
https://webhook.gatsbyjs.com..., you can add them yourself with the following steps.
Wondering what a webhook is or why you need one? Refer to the webhooks reference page.
Webhooks are automatically generated for every Gatsby cloud site. They can be accessed via your Gatsby Cloud instance -> Site Settings -> Webhook. There is a webhook to update your Gatsby preview instance, and another webhook to trigger new builds. Copy the applicable webhook as you’ll need it to get Cosmic JS working swimmingly with Gatsby Cloud.
With the webhook URL you’ve just copied, you should now go into your Cosmic JS bucket and add this webhook for a number of events, notably focusing on creates, updates, and deletes so that your Gatsby Cloud instance stays consistent with Cosmic JS.
Your webhooks will look something like this when finished:
An environment variable references a value that can affect how running processes will behave on a computer, for example in staging and production environments.
You must save environment variables in Gatsby Cloud to authorize your instance to pull source data from Cosmic JS. Gatsby Cloud will fill in Cosmic specific environment variables automatically when you first configure your site (in the Automatic Integration step) by searching your code for used environment variables and pulling the right values from Cosmic JS.
However, you will need to add into Gatsby Cloud any environment variable required for your app to run, such as deployment or test environment configuration settings.
The following Gatsby Cloud-specific environment variables need to be added if you skipped the automatic integration with Cosmic:
Cosmic JS buckets typically have a bucket slug/id as well as a “read key,” both of which can be found Settings -> Basic Settings from the Cosmic JS sidebar.
You will want to grab these values and add them to your Gatsby Cloud instance. A typical naming convention will look like:
|The bucket slug (or bucket id) for the Cosmic JS instance|
|The read key for your Cosmic bucket|
Click “Next” and wait for the first instance to be generated. Now, when you change any copy or content in Cosmic JS, Gatsby Cloud should be up to date with your changes.