https://github.com/f-f/docker-haskell-lavello

🚰 Kitchen-sink docker image for building Haskell in CI
https://github.com/f-f/docker-haskell-lavello

docker haskell nix stack

Last synced: about 1 year ago
JSON representation

🚰 Kitchen-sink docker image for building Haskell in CI

• Host: GitHub
• URL: https://github.com/f-f/docker-haskell-lavello
• Owner: f-f
• License: mit
• Created: 2018-10-28T09:58:26.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2019-11-05T13:09:06.000Z (over 6 years ago)
• Last Synced: 2025-03-31T22:22:28.882Z (over 1 year ago)
• Topics: docker, haskell, nix, stack
• Language: Dockerfile
• Homepage:
• Size: 11.7 KB
• Stars: 6
• Watchers: 2
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# docker-haskell-lavello

🚰 Kitchen-sink docker image for building (stack-based) Haskell projects in CI

IPA: *//laˈvɛllo/*

![lavello](http://img.archiexpo.it/images_ae/photo-g/134-6497057.jpg)

## Where to find this

Docker tags:

- lts-12: `nilrecurring/haskell-lavello:lts-12`

## FAQ

> Wait, don't we have `fpco/stack-build` already?

Yees, and in fact that's our base image.  

Additionally we also `stack build` a whole list of packages, so that when you get to build your project they don't have to be recompiled, dramatically cutting CI time.

> So why isn't this the standard?

The tradeoff here is the bandwidth: the image is quite big (> 1GB), so fetching it from your favorite CI might take some time (especially if you don't cache Docker images).  

Doing this with Haskell is convenient, because compiling things on free-CI CPUs usually takes more time than fetching the already compiled package (YMMV, you'll have to benchmark this with your setup)