Boilerplate code for automatic build and deployment of websites on GitLab CI
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

GitLab CI for Websites

This repository contains boilerplate code for automatic build and deployment of websites on GitLab CI. For now it targets websites built with Jekyll and deployed to Google AppEngine.


For usage with GitLab CI, simply copy .gitlab-ci.yml into your project. To configure the script for your website you need only change the variables declared at the top of the file and then configure your source and repository accordingly. Read on for a quick summary, or see the website for full setup instructions.

For manual usage on your development machine, copy the Makefile and again, configure it as with .gitlab-ci.yml. Note, however, that the makefile assumes that you are already authenticated with a suitable Google account or service account.

You should also copy the app directory and update the production and staging app_*.yaml files appropriately.


Assuming you have not changed the default Jekyll config, you need to change only the following variables:

  • APP_NAME: the name of the Google AppEngine project for your website
  • APP_NAME_STAGING: the name of the Google AppEngine staging project
  • VERSION: is the version string for your app (choose as you see fit)

Directory Structure

The default required directory structure is:

|   .gitlab-ci.yml
|   Makefile
|   ...
├── _site                   (Jekyll output directory)
├── app                     (AppEngine directory)
|     app_production.yaml   (config for production app)
|     app_staging.yml       (config for staging app)
|     www                   (copy of _site created by Makefile/GitLab CI script)

Repository Config

In GitLab settings it will be necessary to define secret variables containing the secret keys of the AppEngine service accounts authorized to deploy to the appropriate AppEngine apps. These variables are


Design Goals

Later a more modular approach will be used, supporting multiple build systems, deployment targets and CI platforms..

Build Systems

Deployment Targets

  • Google AppEngine
  • AWS
  • SFTP

CI Platforms