Soupault generates static sites, so you can host generated pages anywhere. The simplest option is to build your site on your own computer and copy generated pages to the server.

It may not be the easiest option though: you cannot edit your site from a device that doesn’t have a soupault build setup, and you need to remember to rebuild and update the site whenever you make an edit.

The good news is that soupault is easy to integrate into an automated CI setup. Since it comes as a statically linked executable, you only need to download and unpack the archive.

Getting soupault

Since none of the hosting and CI services offer build hosts with preinstalled soupault yet, you’ll need to download it as a part of your website build process.

The primary location for soupault downloads is

However, for a CI process, you may rather want to use a CDN’ed link. For this reason I mirror releases to GitHub. Examples below use GitHub links.


Netlify is a popular static site hosting platform that has a built-in continuous integration service.

One disadvantage is that as of late 2020, Netlify only provides an Ubuntu 16/Xenial build image. If you want to use external programs with soupault, installing their latest versions on older GNU/Linux distros may be somewhat challenging.

On the plus side, Netlify allows rather free-form build scripts and doesn’t make you write fragile YAML files.

First you need a build script.



if [ $? != 0 ]; then
    echo "Error: failed to download soupault."
    exit 1

tar xvf soupault-$SOUPAULT_VERSION-linux-x86_64.tar.gz


Then you need to tell the builder what script to run and which directory to publish. This is specified in the netlify.toml file.

  publish = "build/"
  command = "./"

You can also deploy a website from my sample repo in one click.

GitHub Actions

GitHub Actions is Microsoft GitHub’s built-in CI service.


I use it for building the OCaml book and deploying it to Netlify, so you can use its build script as a basis for your own.

The build part in .github/workflows/main.yml boils down to this:

    # The type of runner that the job will run on
    runs-on: ubuntu-latest

    # Steps represent a sequence of tasks that will be executed as part of the job
    # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
    - uses: actions/checkout@v2

    - name: Install soupault
        SOUPAULT_VERSION: 2.1.0
      run: |
        echo Downloading and unpacking soupault
        tar xvf soupault-$SOUPAULT_VERSION-linux-x86_64.tar.gz
        sudo mv -v ./soupault-$SOUPAULT_VERSION-linux-x86_64/soupault /usr/bin/

    - name: Build the site
      run: |

    # Your deployment steps here