Gatsby Cloud is a product for creating and deploying Gatsby sites fast. Within Gatsby Cloud you can set up your site with custom configuration details.
There are two ways to do this.
.nvmrcfile in your project repository.
NODE_VERSIONenvironment variable inside Gatsby Cloud. The default is
Right now, Gatsby Cloud runs
gatsby build for all site builds.
If you need to run any custom scripts, you can add a
postinstall script to your
package.json and we will run that before or after your packages are installed.
You can! In order to use a monorepo configure your
base directory in Gatsby Cloud Site Settings to the directory you want to build.
yarn, yarn workspaces and
lerna with yarn workspaces or
At the moment, this is not supported.
max-old-space-size is set to
1 GB. If you need to increase this, use the
NODE_OPTIONS environment variable.
Another possibility is that your site uses very large images. It may be necessary to resize the source images.
Currently, in order to use Gatsby Cloud, your project must be using Gatsby version 2.1.0 or greater.
You can authorize specific organizations to be authorized to access Gatsby Cloud. For more information on permissions see the Gatsby Cloud Permissions page.
The goal of Preview is for internal team use, so we do not encourage you to set a publicly accessible domain.
For Builds, the domain is controlled by your deploy target, not Gatsby Cloud. To adjust that deploy target visit your CDN of choice.
You can set an environment variable named
true in Gatsby Cloud and your site will be built with the
assetPrefix set in your
gatsby-config.js. This requires
gatsby-cli version 2.9.0 or higher.
Not at this time. Builds run in the order they’re triggered. and individual builds cannot be cancelled.
Builds are cached by branch. If you want to manually clear the cache and trigger a new build you can do so by clicking on the “Trigger build” dropdown button and selecting the “Clear cache and build master branch” option.