17 Sep 2018 • 4 min read
Disclaimer #1: I wrote this because I had issues getting the beta version of Gatsby (Gatsby 2) working on Netlify. I figured it might help somebody, so I wanted to pay it forward.
Disclaimer #2: This is the 3rd article about Gatsby I’ve written, and I’ll be using code from a previous article. You can walk through that article or just grab the code if you’re walking through this article just to learn about the process.
Disclaimer #3: I bet these steps would work with other types of statically-generated sites, but I’ve never tried. Let me know if you do!
Ready? Here we go! ✈️
Head over to Netlify and get yourself an account, and then confirm your email address. Pretty basic stuff.
Netlify is based around continuous deployment from a Git repo, and they make it easy to pull in a repo from Gitlab, Github, and BitBucket. Since I’m working off of a Github repo for this, I’ll go ahead and connect my Github account:
Then I’ll choose the specific repo that I want to deploy:
Once you’ve selected your repo, you’ll see a screen with a few options, mostly pre-filled for you. If you’re using Gatsby out of the box without any build setting changes, you can leave all of those to their defaults.
Before you hit that ‘Deploy’ button, you need to be aware of 3 gotchas:
Because your environment variables are (most likely) stored in a
.env file and therefore not in source control, they won’t automatically be pulled into Netlify.
Turns out that Netlify will default to Node.js v8 unless you explicitly tell it otherwise. This caused me to have issues when I was trying to deploy a preojct with the latest version of Gatsby. You can solve this one of two ways:
.nvmrcfile to your repo.
I’m feeling lazy, so I decided to go with option #1.
If you’re this far and you still can’t get it to work, try using Yarn instead of NPM. I’m not exactly sure why, but that solved the issue for me.
Now that you know to edit your environment variables before deploying, click “Show Advanced” and start adding any environment variables you need (which will probably be the node version, if not more):
Now you finally get to click that lovely “Deploy site” button.
Once you’ve deployed, you’ll be redirected to your site’s dashboard, and you’ll see that a deployment is in progress:
Give it a few minutes and…
Once you’ve deployed your site, if you like it enough, maybe set up a domain name? Netlify even has a (free!) built in SSL certificate manager, so all you have to do is point your domain at their servers, and they do the rest for you. It’s a piece of cake 🍰.
Get my posts in your feed of choice. Opt-out any time.
If you enjoyed this article, you might enjoy one of these: