Haskell web programming
A Yesod tutorial
update: updated for yesod 1.2
tl;dr: A simple yesod tutorial. Yesod is a Haskell web framework. You shouldn’t need to know Haskell.
Haskell is a high level language and make it harder to shoot you in the foot than
Java for example. One of the best property of Haskell being:
“If your program compile it will be very close to what the programmer intended”.
Haskell web frameworks handle parallel tasks perfectly. For example even better than node.js3.
From the pure technical point of view, Haskell seems to be the perfect web development tool. Weaknesses of Haskell certainly won’t be technical:
- Hard to grasp Haskell
- Hard to find a Haskell programmer
- The Haskell community is smaller than the community for
- There is not yet an heroku for Haskell. In fact, I use heroku to host my websites but this isn’t straightforward (see the how to).
I won’t say these are not important drawbacks. But, with Haskell your web application will have both properties to absorb an impressive number of parallel requests securely and to adapt to change.
Actually there are three main Haskell web frameworks:
I don’t think there is a real winner between these three framework. The choice I made for yesod is highly subjective. I just lurked a bit and tried some tutorials. I had the feeling yesod make a better job at helping newcomers. Furthermore, apparently the yesod team seems the most active. Of course I might be wrong since it is a matter of feeling.
Why did I write this article? The yesod documentation and particularly the book are excellent. But I missed an intermediate tutorial. This tutorial won’t explain all details. I tried to give a step by step of how to start from a five minute tutorial to an almost production ready architecture. Furthermore explaining something to others is a great way to learn. If you are used to Haskell and Yesod, this tutorial won’t learn you much. If you are completely new to Haskell and Yesod it might hopefully helps you. Also if you find yourself too confused by the syntax, it might helps to read this article
During this tutorial you’ll install, initialize and configure your first yesod project. Then there is a very minimal 5 minutes yesod tutorial to heat up and verify the awesomeness of yesod. Then we will clean up the 5 minutes tutorial to use some “best practices”. Finally there will be a more standard real world example; a minimal blog system.
Before the real start
Once done, you need to install yesod. Open a terminal session and do:
There are few steps but it should take some time to finish.
You are now ready to initialize your first yesod project. Open a terminal and type:
Enter your name, choose
yosog for the project name and enter
Yosog for the name of the Foundation. Finally choose
sqlite. Now, start the development cycle:
This will compile the entire project. Be patient it could take a while the first time. Once finished a server is launched and you could visit it by clicking this link:
Congratulation! Yesod works!
Note: if something is messed up use the following command line inside the project directory.
Until the end of the tutorial, use another terminal and let this one open in a corner to see what occurs.
Of course this step is not mandatory for the tutorial but it is a good practice.
Fortunately, there is already a
.gitignore file into the
yosog folder. You just have to initialize your git repository:
We are almost ready to start.
Some last minute words
Up until here, we have a directory containing a bunch of files and a local web server listening the port 3000. If we modify a file inside this directory, yesod should try to recompile as fast as possible the site. Instead of explaining the role of every file, let’s focus only on the important files/directories for this tutorial:
||is where you’ll configure the map url → Code.|
||contains the files that will contain the code called when a url is accessed.|
||contains html, js and css templates.|
||is where you’ll configure the persistent objects (database tables).|
During this tutorial we’ll modify other files as well, but we won’t explore them in detail.
Also note, shell commands are executed in the root directory of your project instead specified otherwise.
We are now ready to start!
To verify the quality of the security of the yesod framework, let’s make a minimal echo application.
Make a server that when accessed
/echo/[some text]should return a web page containing “some text” inside an
~/Sites/yosog $ yesod add-handler Name of route (without trailing R): Echo Enter route pattern (ex: /entry/#EntryId): /echo/#String Enter space-separated list of methods (ex: GET POST): GET
Almost all work is done for us. The
add-handler do the following:
config/route file by appending:
/echo/#String EchoR GET
This line contains three elements: the url pattern, a handler name, an http method.
- create a
Handler.Echoin the main
Handler.Echoin the cabal file for building the application
Now try to go to
localhost:3000/echo/foo. You should get a message explaining
getEchoR is not yet implemented.
So let’s take a look at
This should be straightforward. Now we changes it by:
Don’t worry if you find all of this a bit cryptic. In short it just declare a function named
getEchoR with one argument (
theText) of type
String. When this function is called, it return a
Handler RepHtml whatever it is. But mainly this will encapsulate our expected result inside an html text.
After saving the file, you should see yesod recompile the application. When the compilation is finished you’ll see the message:
Starting devel application.
Now you can visit:
TADA! It works!
Even this extremely minimal web application has some impressive properties. For exemple, imagine an attacker entering this url:
You can click on it to test it.
The special characters are protected for us. A malicious user could not hide some bad script inside.
This behavior is a direct consequence of type safety. The url string is put inside a url type. Then the interesting part in the url is put inside a String type. To pass from url type to String type some transformation are made. For example, replace all “
%20” by space characters. Then to show the String inside an html document, the string is put inside an html type. Some transformations occurs like replace “
<” by “
<”. Thanks to yesod, this tedious job is done for us.
Yesod is not only fast, it helps us to remain secure. It protects us from many common errors in other paradigms. Yes, I am looking at you PHP!
Even this very minimal example should be enhanced. We will clean up many details:
- Put our “views”4 inside the
It is a good practice to use
Data.Text instead of
To declare it, add this import directive to
Foundation.hs (just after the last one):
We have to modify
config/routes and our handler accordingly. Replace
/echo/#Text EchoR GET
And do the same in
Some html (more precisely hamlet) is written directly inside our handler. We should put this part inside another file. Create the new file
and modify the handler
At this point, our web application is nicely structured. We use
Data.Text and our views are in templates. It is the time to make a slightly more complex example.
Let’s make another minimal application. You should see a form containing a text field and a validation button. When you enter some text (for example “Jormungad”) and validate, the next page present you the content and its reverse appended to it. In our example it should return “JormungaddagnumroJ”.
First, add a new handler:
~/Sites/yosog (master) $ yesod add-handler Name of route (without trailing R): Mirror Enter route pattern (ex: /entry/#EntryId): /mirror Enter space-separated list of methods (ex: GET POST): GET POST
This time the path
/mirror will accept GET and POST requests. Update the corresponding new Handler file (
We will need to use the
reverse function provided by
Data.Text which explain the additional import.
The only new thing here is the line that get the POST parameter named “content”. If you want to know more detail about it and form in general you can take look at the yesod book.
Create the two corresponding templates (
And that is all. This time, we won’t need to clean up. We may have used another way to generate the form but we’ll see this in the next section.
Just try it by clicking here.
Also you can try to enter strange values (like
<script>alert('Bad');</script>). Like before, your application is quite secure.
We saw how to retrieve http parameters. It is the time to save things into a database.
This example will be very minimal:
/blogshould display the list of articles,
/blogshould create a new article,
/blog/<article id>should display the content of the article.
As before add some handlers
~/Sites/yosog (master) $ yesod add-handler Name of route (without trailing R): Blog Enter route pattern (ex: /entry/#EntryId): /blog Enter space-separated list of methods (ex: GET POST): GET POST ~/Sites/yosog (master) $ yesod add-handler Name of route (without trailing R): Article Enter route pattern (ex: /entry/#EntryId): /blog/#ArticleId Enter space-separated list of methods (ex: GET POST): GET
Then we declare another model object. Append the following content to
Article title Text content Html deriving
Html is not an instance of
Eq, we had to add the
deriving line. If you forget it, there will be an error.
After the route and the model, we write the handler. Let’s write the content of
Handler/Blog.hs. We start by declaring the module and by importing some block necessary to handle Html in forms.
Remark: it is a best practice to add the YesodNic instance inside
Foundation.hs. I put this definition here to make things easier but you should see a warning about this orphan instance. To put the include inside Foundation.hs is left as an exercice to the reader.
Hint: Do not forget to put
nicHtmlField inside the exported objects of the module.
This function defines a form for adding a new article. Don’t pay attention to all the syntax. If you are curious you can take a look at Applicative Functor. You just have to remember
areq is for required form input. Its arguments being:
areq type label default_value.
-- The view showing the list of articles getBlogR :: Handler RepHtml getBlogR = do -- Get the list of articles inside the database. articles <- runDB $ selectList  [Desc ArticleTitle] -- We'll need the two "objects": articleWidget and enctype -- to construct the form (see templates/articles.hamlet). (articleWidget, enctype) <- generateFormPost entryForm defaultLayout $ do $(widgetFile "articles")
This handler should display a list of articles. We get the list from the DB and we construct the form. Just take a look at the corresponding template:
You should remark we added some logic inside the template. There is a test and a “loop”.
Another very interesting part is the creation of the form. The
articleWidget was created by yesod. We have given him the right parameters (input required or optional, labels, default values). And now we have a protected form made for us. But we have to create the submit button.
You could take a first look by clicking here. Of course, you could not post something yet.
Get back to
postBlogR :: Handler RepHtml postBlogR = do ((res,articleWidget),enctype) <- runFormPost entryForm case res of FormSuccess article -> do articleId <- runDB $ insert article setMessage $ toHtml $ (articleTitle article) <> " created" redirect $ ArticleR articleId _ -> defaultLayout $ do setTitle "Please correct your entry form" $(widgetFile "articleAddError")
This function should be used to create a new article. We handle the form response. If there is an error we display an error page. For example if we left some required value blank. If things goes right:
- we add the new article inside the DB (
runDB $ insert article)
- we add a message to be displayed (
setMessage $ ...)
- we are redirected to the article web page.
Here is the content of the error Page:
Finally we need to display an article. For this we will modify
get404 function try to do a get on the DB. If it fails it return a 404 page. The rest should be clear. Here is the content of
The blog system is finished. Just for fun, you can try to create an article with the following content:
This is the end of this tutorial. I made it very minimal.
If you already know Haskell and you want to go further, you should take a look at the recent i18n blog tutorial. It will be obvious I inspired my own tutorial on it. You’ll learn in a very straightforward way how easy it is to use authorizations, Time and internationalization.
If, on the other hand you don’t know Haskell. Then you shouldn’t jump directly to web programming. Haskell is a very complex and unusual language. My advice to go as fast as possible in using Haskell for web programming is:
- Start by try Haskell in your browser
- Read my tutorial Learn Haskell Fast and Hard on School of Haskell or directly on this blog
- Then read the excellent Learn you a Haskell for Great Good
- If you have difficulties in understanding concepts like monads, you should really read these articles. For me they were enlightening.
- If you feel confident, you should be able to follows the yesod book and if you find difficult to follows the yesod book, you should read real world Haskell first.
Also, note that:
- haskell.org is full of excellent resources.
- hoogle will be very useful
- Use hlint as soon as possible to get good habits.
As you should see, if you don’t already know Haskell, the path is long but I guaranty you it will be very rewarding!
ps: You can download the source of this yesod blog tutorial at github.com/yogsototh/yosog.
One can argue these benchmark contains many problems. But the benchmarks are just here to give an order of idea. Mainly Haskell is very fast.↩
Generally high level Haskell is slower than C, but low level Haskell is equivalent to C speed. It means that even if you can easily link C code with Haskell, this is not needed to reach the same speed. Furthermore writing a web service in C/C++ seems to be a very bad idea. You can take a look at a discussion on HN about this.↩
By view I mean yesod widget’s hamlet, lucius and julius files.↩