-
I tried the second option a few years ago but have not tried the third one. I have been using the first one, using classic Nix. Only recently, I have refactored some of my projects to use Nix Flakes. Today, I also refactored my Haskell project template to use Flakes.
-
AppSignal
AppSignal knows why the f*#k it crashed. Stop vibe-debugging. Every exception, every backtrace, grouped so you see patterns, not noise.
-
I am pretty sure that there are many better ways to do what I do in this template repository, but I am happy using it to quickly spin up a new Haskell project. There are quite a few other things and methods I use in real-life projects, such as multi-package builds and GitHub Release Please Action integration, which are quite easy to add upon this template.
-
If you find this template useful, consider starring the repository or bookmarking it for future reference. You might also want to check out my new Nix Flake Templates collection, where I plan to share more Haskell setups as my use cases expand.
-
Haskell has been my go-to language for over 7 years. First, I started with Stack, then switched to plain Cabal and finally settled on Nix to provision a development environment for Haskell projects.
-
Haskell.nix -- a more flexible but complex option from IOHK.
-
haskell-flake -- a recent and modular setup based on flake-parts.
-
haskell-flake -- a recent and modular setup based on flake-parts.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives