Yesod deployment manager
Haskell Shell
Pull request Compare This branch is 233 commits behind snoyberg:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.

Deployment system for Yesod (and other Haskell) web apps.

Quick Start

Do get Keter up-and-running quickly on an Ubuntu system, run:

wget -O - | bash

(Note: you may need to run the above command twice, if the shell exits after apt-get but before running the rest of its instructions.) This will download and build Keter from source and get it running with a default configuration.


Instructions are for an Ubuntu system. Eventually, I hope to provide a PPA for this (please contact me if you would like to assist with this). For now, the following steps should be sufficient:

First, install PostgreSQL

sudo apt-get install postgresql

Second, build the keter binary and place it at /opt/keter/bin. To do so, you'll need to install the Haskell Platform, and can then build with cabal. This would look something like:

sudo apt-get install haskell-platform
cabal update
cabal install keter
sudo mkdir -p /opt/keter/bin
sudo cp ~/.cabal/bin/keter /opt/keter/bin

Third, create a Keter config file:

# /opt/keter/etc/keter-config.yaml
root: ..
# host: host to bind to
# port: port to listen on
# setuid: myname
# ssl:
#   host:
#   port:
#   key:
#   certificate:
# reverse-proxy:
#  - reversed-host: some-internal-site
#    reversed-port: 80
#    reversing-host:
#    ssl: whether the reversed host uses SSL (defaults to False)
#    # response headers can be rewritten as follows:
#    rewrite-response:
#      - header: Location
#        from: ^
#        to:
#    # request headers can be rewritten as well, though less likely
#    # to be used.
#    rewrite-request:
#      - header: X-SomeApplicationHeader
#        from: ^
#        to:
# # Header rewriting supports POSIX regular expressions in the "from" and
# # supports referencing matched groups in the "to" with "\1", "\2", ...

Fourth, set up an Upstart job to start keter when your system boots.

# /etc/init/keter.conf
start on (net-device-up and local-filesystems and runlevel [2345])
stop on runlevel [016]

console none

exec /opt/keter/bin/keter /opt/keter/etc/keter-config.yaml

Finally, start the job for the first time:

sudo start keter

Optionally, you may wish to change the owner on the /opt/keter/incoming folder to your user account, so that you can deploy without sudoing.

sudo mkdir -p /opt/keter/incoming
sudo chown $USER /opt/keter/incoming


An application needs to be set up as a keter bundle. This is a GZIPed tarball with a .keter filename extension and which has one special file: config/keter.yaml. A sample file is:

exec: ../dist/build/yesodweb/yesodweb
    - production
host: # can replace with "*" to be the default app
ssl: false # true would use https scheme for approot

# Additional hosts your app will listen on, without affecting approot.

# Static file hosts. Keter handles the serving for you.
    - host:
      root: ../static # relative to config file, just like the executable

# Host name redirects.
    - from:

Keter as well supports wildcard subdomains and exceptions, as in this example configuration:

exec: ../
    - Hello World 1
    - "*"
    - host:
      root: ../static
    - from:

Due to YAML parsing, wildcard hostnames will need to be quoted as above. Wildcard hostnames are not recursive, so must be explicitly added as an extra hostname in the above example, or alternatively, *.* would cover all host names two levels deep. It would not cover host names only one level deep, such as In this manner, wildcard hostnames correspond to the manner in which SSL certificates are handled per RFC2818. Wildcards may be used in only one level of a hostname, as in foo.*

Full RFC2818 compliance is not present - f* will not be handled as a wildcard with a prefix.

A sample Bash script for producing a Keter bundle is:

#!/bin/bash -ex

cabal build
strip dist/build/yesodweb/yesodweb
rm -rf static/tmp
tar czfv yesodweb.keter dist/build/yesodweb/yesodweb config static

For users of Yesod, The yesod executable provides a keter command for creating the bundle, and the scaffolded site provides a keter.yaml file.


In order to deploy, you simply copy the keter bundle to /opt/keter/incoming. To update an app, copy in the new version. The old process will only be terminated after the new process has started answering requests. To stop an application, delete the file from incoming.