This guide was most recently updated on Oct 17th 2017. Below are the package versions used:
- Ruby 2.3.1
- Middleman 4.2.1
Screenshots may be outdated.
In this tutorial we’ll take a look at how to host Middleman on Netlify, including setting up continuous deployment.
Let’s start from scratch. If you already have a Middleman site set up, you can skip straight to the Connecting to Netlify section.
In this post
Open your terminal, and enter the following commands:
gem install middleman middleman init my-site
Once everything is installed, it’s time to push it to your repo of choice. Directions for GitHub follow here.
Creating your Git Repo
Create a new repository on GitHub. To avoid errors, do not initialize the new repository with README, license, or gitignore files. You can add these files after your project has been pushed to GitHub.
Open Terminal (for Mac users) or the command prompt (for Windows and Linux users).
For our purposes, let’s call your new repo “middleman”.
Change the current working directory to your local project.
$ cd ./my-site
Initialize the local directory as a Git repository.
$ git init
Add the files in your new local repository. This stages them for the first commit.
$ git add .
Commit the files that you’ve staged in your local repository.
git commit -m 'First commit'
At the top of your GitHub repository’s Quick Setup page, click the clipboard icon to copy the remote repository URL.
In Terminal, add the URL for the remote repository where your local repository will be pushed.
git remote add origin Git_Repository_URL
Verify your URL
git remote -v
Now, it’s time to push the changes in your local repository to GitHub.
git push origin master
Now that your assets are up and running on GitHub, let’s connect them to Netlify.
Configuring some prerequisites for Netlify
Netlify will, unless told otherwise, use some default versions of build tools, and our build environment is fairly bare. So, let’s set things to match your local versions and get dependencies installed.
- set a Ruby version. Commit a
/.ruby-versionfile to your repository containing the version closest to your local. Versions available in the build environment are listed in this documentation
- commit a Gemfile and Gemfile.lock. What you’ll want in there and how to create it is listed in this post (specifically you need
gem "middleman"in your Gemfile and then to run
bundle installand commit the resulting files).
Connecting to Netlify
Step 1: Add Your New Site
Creating a new site on Netlify is simple. Once you’ve logged in, you’ll be taken to https://app.netlify.com/sites. If you’re just starting out, there’s only one option.
Step 2: Link to Your GitHub
Clicking “New Site” brings you to this screen:
When you push to GitHub, Netlify does all the work. No more manual deploying of updates or changes!
Since your assets are hosted on GitHub, we’ll need to link Netlify to GitHub. Click “Link to GitHub”.
Step 3: Authorize Netlify
It’s time to allow Netlify and GitHub to talk to each other. Clicking the “Authorize Application” button will do just that. Like it says in the image below, Netlify doesn’t store your GitHub access token on our servers. If you’d like to know more about the permissions Netlify requests and why we need them, you can visit https://docs.netlify.com/github-permissions/.
Step 4: Choose Your Repo
Now that you’ve connected Netlify and GitHub, you can see a list of your Git repos. There’s the “middleman” repo we just pushed to GitHub. Let’s select it.
Step 5: Configure Your Settings
Here you can configure your options. For the purposes of this tutorial, there’s nothing you need to change, so just click “Save”.
Step 6: Build Your Site
Now it’s time to sit back and relax. Go grab something cold to drink, scratch the dog behind the ears, or just get up and walk around (you’ve probably been in front of the computer for too long today, right?). Netlify will do the rest, and you can watch the progress.
Step 7: Done
Wait, you thought there was going to be more? Nope! Netlify has done it all for you, including giving your site a temporary name. Let’s make it look a little prettier:
There, that’s better. Now you can add your custom domain, and your site will be live for your adoring public to view. Congratulations, and thanks for using Netlify!
… … …
no post credits sequence. No Easter Egg. It’s finito.