Automating Nikola rebuilds with Travis CI

In this guide, we’ll set up Travis CI to rebuild a Nikola website and host it on GitHub Pages.


By using Travis CI to build your site, you can easily blog from anywhere you can edit text files. Which means you can blog with only a web browser and You also won’t need to install Nikola and Python to write. Or a real computer, a mobile phone could probably access one of those services and write something.


  • The build might take a couple minutes to finish (1:30 for the demo site; YMMV)
  • When you commit and push to GitHub, the site will be published unconditionally. If you don’t have a copy of Nikola for local use, there is no way to preview your site.

What you need

  • A computer for the initial setup that can run Nikola and the Travis CI command-line tool (written in Ruby) — you need a Unix-like system (Linux, OS X, *BSD, etc.); Windows users should try Bash on Ubuntu on Windows (available in Windows 10 starting with Anniversary Update) or a Linux virtual machine.
  • A GitHub account (free)
  • A Travis CI account linked to your GitHub account (free)

Setting up Nikola

Start by creating a new Nikola site and customizing it to your liking. Follow the Getting Started guide. You might also want to add support for other input formats, namely Markdown, but this is not a requirement.

After you’re done, you must configure deploying to GitHub in Nikola. Make your first deployment from your local computer and make sure your site works right. Don’t forget to set up .gitignore. Moreover, you must set GITHUB_COMMIT_SOURCE = False — otherwise, Travis CI will go into an infinite loop.

If everything works, you can make some change to your site (so you see that rebuilding works), but don’t commit it just yet.

Setting up Travis CI

Next, we need to set up Travis CI. To do that, make sure you have the ruby and gem tools installed on your system. If you don’t have them, install them from your OS package manager.

First, download/copy the .travis.yml file (note the dot in the beginning; the downloaded file doesn’t have it!) and adjust the real name, e-mail (used for commits; line 12/13), and the username/repo name on line 21. If you want to render your site in another language besides English, add the appropriate Ubuntu language pack to the list in this file.

travis.yml (Source)

# Travis CI config for automated Nikola blog deployments
language: python
cache: apt
sudo: false
    - language-pack-en-base
- 3.5
- git config --global 'Travis CI'
- git config --global [email protected]'
- git config --global push.default 'simple'
- pip install --upgrade pip wheel
- echo -e 'Host\n    StrictHostKeyChecking no' >> ~/.ssh/config
- eval "$(ssh-agent -s)"
- chmod 600 id_rsa
- ssh-add id_rsa
- git remote rm origin
- git remote add origin
- git fetch origin master
- git branch master FETCH_HEAD
- pip install 'Nikola[extras]'
- nikola build && nikola github_deploy -m 'Nikola auto deploy [ci skip]'
        on_success: change
        on_failure: always

Next, we need to generate a SSH key for Travis CI.

echo id_rsa >> .gitignore
echo >> .gitignore
ssh-keygen -C TravisCI -f id_rsa -N ''

Open the file and copy its contents. Go to GitHub → your page repository → Settings → Deploy keys and add it there. Make sure Allow write access is checked.

And now, time for our venture into the Ruby world. Install the travis gem:

gem install --user-install travis

You can then use the travis command if you have configured your $PATH for RubyGems; if you haven’t, the tool will output a path to use (eg. ~/.gem/ruby/2.0.0/bin/travis)

We’ll use the Travis CI command-line client to log in (using your GitHub password), enable the repository and encrypt our SSH key. Run the following three commands, one at a time (they are interactive):

travis login
travis enable
travis encrypt-file id_rsa --add

Commit everything to GitHub:

git add .
git commit -am "Automate builds with Travis CI"

Hopefully, Travis CI will build your site and deploy. Check the Travis CI website or your e-mail for a notification. If there are any errors, make sure you followed this guide to the letter.


Comments powered by Disqus