How To Password Protect A Jekyll Site

Saturday, Feb 18, 2017

You’ve got a Jekyll site, and now you’re wondering how to password protect some or all of the content. Perhaps the site is under development and you want to make it viewable to only your client for review. You could set something up on Heroku, but that’s expensive and total overkill for a simple password form. When you made the smart move to a static generator instead of some CMS, presumably one of your goals was to negate the need for servers and databases altogether.

Well, the good news is that, with Aerobatic, you can create a login page for your Jekyll site with just a few lines of code. No servers. No dynos. No hassles. Want to see how easy it is? Let’s go…

Create a login.html

In your Jekyll site, you’ve got an index.html in the root folder. Make a copy of that file and call it login.html. Replace the content of the login.html file with code similar to below. You can style your login page however you want. What’s essential is that the form markup needs to be decorated with the aerobatic-password attribute in the input as shown below.

<!DOCTYPE html>
<html lang="en">
    <body class="body">
        <div class="container">
            <header class="header">
                <h1>Jekyll Auth<span>No servers required.</span></h1>
            <div class="content center">
                <!-- login form -->
        <h6 class="error" id="password-error" style="color:red"><strong></strong></h6>
        <form method="POST">
          <label for="password">Password</label>
          <input class="u-full-width" type="password" placeholder="password" name="aerobatic-password" id="aerobatic-password">
            <input class="button-primary" type="submit" value="Submit">
                <!-- /form -->
        <!-- /container -->
        <!-- JS -->
            if (/fail=1/.test( {
              document.getElementById("password-error").innerHTML= "Incorrect Password" ;

Create Aerobatic site

Assuming you’ve already installed the aerobatic-cli, from the command line, enter the following to associate your Jekyll site with Aerobatic:

aero create

Edit aerobatic.yml

This is where you’ll take advantage of Aerobatic’s built-in password-protect plugin. In the root of your Jekyll site, open up the newly created aerobatic.yml file and edit like so:

# Aerobatic website manifest
  - name: password-protect
      password: $SITE_PASSWORD
      loginPage: login.html
      maxFailures: 5
      failureWindow: 600
      lockoutDuration: 600
        - '/css/*.css'
        - '/js/*.js'
        - '/img/*.jpg'
  - name: webpage

You’ll notice here a couple of things. The first is that we have an environment variable called $SITE_PASSWORD. The second thing you probably noticed is that we’re telling the password-protect plugin to not protect a few files, namely some CSS, JS, and JPG files. That’s so they can load on the login.html page and not get a 401 error before the password has been entered.

Create environment variable

Login to the Aerobatic dashboard, and navigate to your site’s settings. Enter a value for your newly created environment variable. In this example, the SITE_PASSWORD variable has a value of aerobatic.

Aerobatic Environment Variable

The demo site for adding a custom login page can be found at and the source code is on Bitbucket.

Set up Bitbucket Pipelines Continuous Deployment

At this point you could just type aero deploy -d _site to deploy your site. However, in this case, we’re going to use Bitbucket Pipelines to set up a nice continuous deployment flow. Make sure you enable Bitbucket Pipelines in your repo, and here’s what your bitbucket-pipelines.yml file might look like (you may have noticed we’re using Aerobatic’s custom docker image for Jekyll:

image: aerobatic/jekyll
      - step:
            - jekyll build
            - aero deploy --directory _site

Push your changes

Either from the command line, or with a tool like Sourcetreee, push the changes to your Jekyll repository. e.g.

git add --all
git commit -m "Added a login page"
git push origin master


And that’s it! The demo site for adding a custom login page can be found at and the source code is on Bitbucket.