How to deploy a Jekyll website

Finding an efficient way to deploy an Angular application can be tricky, especially if you aren’t able to run the commands to generate a production build on the server, like on shared hosting via FTP, Amazon S3 or Rackspace Cloud Files.

You can get around this issue by generating the production build locally and uploading the files to each server manually. However, there are several downsides to this approach.

  • Everyone on your team needs to have server credentials saved and kept in sync on their own machine. This has security implications, in addition to being incredibly frustrating.
  • If anyone wants to deploy a change, all the necessary dependencies need to be installed (like Ruby or Bundler) in order to generate a new production build.
  • As building locally is a manual process, it’s far more time consuming process in addition to being much more susceptible to errors.

DeployHQ was designed to help developers solve these problems. Create custom recipes to automate your deployment process for your Jekyll projects!

All you need to do is create a project, add a server and configure a couple of build commands.

Getting started

If you haven’t already created a DeployHQ account, you’ll need to signup for a new account.

Note: You can deploy 1 project up to 10 times a day on the free plan!

Once you’re logged in, head to the Projects tab and click New Project.

The project creation screen

Follow the wizard to connect your repository to your project. Don’t panic if your repository hosting provider isn’t listed, as you can manually enter your repository details.

If you’re having any difficulty, please check out this article on our support centre.

Setup a server

DeployHQ needs to know where you want your website to be uploaded.

The server creation screen

Choose the protocol and enter the required server information.

Adding the build commands

Next, we’ll need to add the commands that need to be run in order to produce a production build of your website. They’ll each be executed in order on a secure, isolated environment which comes pre-installed with Ruby and Bundler.

Choose Build Commands from the sidebar, then click New Build Command.

You’ll only need to add the following build commands to build a Jekyll website.

  • bundle install --deployment
  • JEKYLL_ENV=production bundle exec jekyll build

The --deployment flag tells Bundler to store gems in a vendor/ directory. This allows for dependencies to be cached between builds for faster deployment times.

Configure build caching

By default DeployHQ will automatically start from a clean state on every deployment. This often increases the time it takes to build your Jekyll project as the entire vendor directory will need to be re-downloaded on every deployment.

To avoid this from happening, DeployHQ allows you can specify a list of files and folders that should be preserved between each deployment.

Select Build Configuration at the top of the build pipeline area, then click New Cached File under Cached Build Files.

Enter vendor/** and save.

Change the Deployment Subdirectory

Finally, we need to update the project’s Deployment Subdirectory to point to the folder where the production output is generated.

Choose Configuration under the Repository heading in the sidebar, then scroll down to Deployment Subdirectory.

Simply enter _site and press save.

Run your first deployment

That’s all the configuration done — time to deploy!

Click Deploy Project in the header.

The server you created should be preselected, along with the start and end revisions. Once you’re happy with everything, scroll down and click Deploy to begin the deployment.

Now sit back, relax and look very smug. You’ve just saved yourself bags of time.

The deployment completion screen

Proudly powered by Katapult. Running on 100% renewable energy.