Rewriting to Haskell–Deployment

Posted on March 14, 2020 by Riccardo

Rewriting to Haskell (Series)

Rewriting to Haskell–IntroRewriting to Haskell–Project SetupRewriting to Haskell–DeploymentRewriting to Haskell–Automatic FormattingRewriting to Haskell–ConfigurationRewriting to Haskell–Standing on the shoulders of RailsRewriting to Haskell–Making GHC More NitpickyRewriting to Haskell–TestingRewriting to Haskell–LintingRewriting to Haskell–Parsing Query ParamsRewriting to Haskell–Parsing Query Params, AgainRewriting to Haskell–Errors

Deploy with Hapistrano

Stream was born as a Rails application. For that reason, we have been using Capistrano to deploy it. That's why for the Servant code we have decided to employ Hapistrano:

Hapistrano makes it easy to reliably deploy Haskell applications to a server.

Following popular libraries like Ruby's < Capistrano>, Hapistrano does the work of building the application with dependencies into a distinct folder, and then atomically moves a symlink to the latest complete build.

This allows for atomic switchovers to new application code after the build is complete. Rollback is even simpler, since Hapistrano can just point the current symlink to the previous release.

This is how we are currently using Hapistrano to deploy the code:

hap deploy
# or
HAPISTRANO_REVISION=origin/feature_branch hap deploy

What follows is our hap.yaml:

deploy_path: '/home/stream/application-hs'
  - "-A" # SSH agent forwarding
repo: ''
revision: "_env:HAPISTRANO_REVISION:origin/master"
  - cd haskell && stack setup
  - cd haskell && stack build
  - cd haskell && stack install --local-bin-path .
restart_command: sudo systemctl restart stream-hs


First of all, we need to have Stack installed. This is needed because, with the above configuration, Hapistrano will build the app on the server on each deploy.

sudo wget -qO- | sh

Secondly, we decided that, for the time being, we will be serving the Servant code under /servant. Also, our Servant app will be running on port 8080. So let's have Nginx do the right thing:

location /servant {

Thirdly, we want Systemd to manage the Servant process. What follows is the unit configuration we are using:

Description=Servant App

#                      ^ `deploy_path` for Hapistrano.
#                                     ^ `current` is where Hapistrano keeps the latest deployed app.
#                                             ^ We keep the Servant code in the repo in the `haskell/` folder.
#                                                     ^ Name of the executable.


Notice that haskell-exe lives inside the current release (i.e. latest) because we configure Hapistrano to stack install --local-bin-path . .

Lastly, we need to allow the stream user to restart the application by adding them to /etc/sudoers:

stream ALL=(ALL) NOPASSWD: /bin/systemctl restart stream-hs

We automated all of the steps with Ansible.

We invoke it with:

- role: haskell
  haskell__app_name: stream
  haskell__username: stream

And here's the role:

- name: Install Stack
  shell: "sudo wget -qO- | sh"
    creates: "/usr/local/bin/stack"

- name: Configure Nginx
    src: "{{ item }}"
    dest: "/etc/nginx/snippets/{{ haskell__app_name }}/{{ item }}"
    - haskell.conf
  notify: reload nginx

- name: Create haskell service in Systemd
    src: haskell.service.j2
    dest: /etc/systemd/system/{{ haskell__app_name }}-hs.service
    mode: 0644

- name: Enable haskell service in Systemd
    name: "{{ haskell__app_name }}-hs"
    enabled: yes
    daemon_reload: yes
    state: started

- name: Allow user to restart the application
    dest: /etc/sudoers
    state: present
    line: "{{ haskell__username }} ALL=(ALL) NOPASSWD: /bin/systemctl restart {{ haskell__app_name }}-hs"


It's one of the selected few I follow every week – Mateusz

Tired of RELEARNING webdev stuff?

  • A 100+ page book with the best links I curated over the years
  • An email once a week full of timeless software wisdom
  • Your recommended weekly dose of pink
  • Try before you buy? Check the archives.