Before we start writing any code, let's ensure our environment is setup
properly.
1. Install the dependencies
The easiest way to build H...
For further actions, you may consider blocking this person and/or reporting abuse
Thanks' for putting this together. I've glanced over post 2 as well, which I'm working on now. I hit a block when it came to the custom docker environment though:
1) > First, we're going to make our own container image for building our Haskell
application. Let's call it dockerfiles/buildenv.
Does this mean I need to register a new image called that on docker hub? Making a file at
haskelltutorial/dockerfiles/buildenvdoesn't seem to be doing the trick.2) GitLab Ci now prompts me to enter some key value pairs and manually trigger the build. What key values is it expecting?
Hi Dave,
You don't need to use your own container image at all, if you're not familiar with docker and Gitlab CI it's better to skip that step and use the default image. Learn one thing at a time ;-)
The reason gitlab CI/docker explanations are even in there is that it can be tricky to setup a Haskell pipeline "correctly". If you have no caches, builds are going to take a looooong time. But there are better people to learn those technologies from.
Ai, bugger, looks like dev.to and pandoc handle markdown to html conversion differently. Series only works once I have multiple entries ;-)
I keep running into this - makes me sad.
We need a markdown to markdown converter!
For ligatures, using FiraCode (font) suffices
That is one way to do it, but I believe the IDE must still support ligatures.