My last post covered WebSockets within the Ruby ecosystem with a particular focus on the support for WebSockets within Rails. As I was learning about the complex relationship between WebSockets and Ruby, I found a web framework that makes WebSockets easier while still letting us do things the “Rails way”. It’s called Phoenix. Although WebSockets is how I discovered Phoenix, it has a lot more to offer than just “easier WebSockets”.

Unfortunately (or fortunately, depending on how you look at things), Phoenix isn’t a Ruby framework. Instead, it is written and based in a language called Elixir that’s built on top of the Erlang virtual machine. In this article, we’ll take a look at why it makes sense to consider the Elixir+Phoenix combo as a Rubyist as well as the basics of the Phoenix framework.

Elixir

In order to understand what makes Elixir special, we have to understand a little bit about Erlang and the Erlang VM. Erlang was originally developed at Ericsson (which is, more or less, a telecom company) to build systems that stay up no matter what kind of madness is going on in the world. Although Erlang didn’t catch on like the plague, it’s been used for some pretty big projects by a lot of companies. Some examples: WhatsApp is powered by an Erlang-based architecture, Facebook initially used Erlang for its chat architecture and Basho (the company behind Riak) uses Erlang heavily and holds it in high regard. There are a number of reasons why Erlang is so good for building highly available distributed systems (e.g. the concept of supervisors is executed particularly well within Erlang). However, Erlang is a functional language with a number of idiosyncrasies that make it a bit unpleasant to use, for many.

Erlang runs on top of the Erlang Virtual Machine. If you’re familiar with Java, this is similar to the relationship between Java and the JVM. Elixir is another language that runs on top of the Erlang Virtual Machine. So, Elixir offers incredibly easy interop with Erlang (we can call Erlang functions at essentially no runtime cost) with a different syntax which, in my opinion, is more pleasing than the Erlang syntax.

If you’d like to quickly get up to speed with the basics of Elixir, we have a couple of articles you can skim through quickly. Even if you don’t have any experience with Elixir, but have some Ruby background, you’ll find that it isn’t too difficult to catch on to the Elixir way of things.

Phoenix

So, what is Phoenix? It’s a Rails-like framework built for Elixir. You might ask: what on Earth is the point of learning yet another framework for yet another language that nobody really seems to be using (yet)? There are a couple of reasons. First of all, the Erlang VM is pretty darn fast and Elixir inherits this speed. There are benchmarks that show this. But of course, we can sit around all day and poke holes in those so you’ll just have to build something with both technologies to believe it.

Secondly, Elixir is an interesting language because it manages to combine functional programming, OOP, and a Lisp-like conception of metaprogramming (Elixir’s macros are pretty insanely powerful). Finally, Rails definitely feels a bit behind-the-curve when it comes to things like WebSockets. Phoenix comes with these right of the box. Best of all, you get most of these benefits without having to leave the niceties of Rails behind. Granted, there aren’t as many packages for Phoenix as there are for Rails but the framework itself is fairly feature-complete. Let’s take a look at the basics of Phoenix.

Installation

We’ll zip through the installation steps mostly because they’re boring and there are other resources that probably explain them better (and we’ll link to these). First of all, you need to install Elixir which, fortunately, has a pretty coherent Install page. The Elixir equivalent of the RubyGems/Bundler couple is called “Mix”. We can use that to install Phoenix, as described on the Phoenix Install Page.

Build it

If I threw a bunch of theory at you, you’d probably forget nearly all of it by the time you finish reading this article. Instead, we’re going to build a small application with Phoenix to see how the sausage is made. If you follow along, the steps might seem a bit disconnected and random at first, but eventually, things should “click.”

So, what are we going to build? I’m constantly forgetting little things throughout the day and I’d like a way to be reminded while I’m banging out some code on my laptop. To solve this problem, we’re going to build a webapp that we can set reminders on and it’ll remind us via email. We could also do this with the HTML5 Notifications API, but we’ll demonstrate some important concepts within Phoenix with the email.

Basic Structure

We start out with an “empty” Phoenix app by running:

mix phoenix.new remynders

You should get an install message that ends with this:

We are all set ! Run your Phoenix application: $ cd remynders $ mix phoenix.server

You can also run it inside IEx (Interactive Elixir) as:

$ iex -S mix phoenix.server

We can take a look at what we have so far after starting the server at http://127.0.0.1:4000. We can leave the server running because, just like Rails, the Phoenix server does live code reload. In order to get going with our “remynders” app, we have to modify the routing so that we can have a route that doesn’t end up at the Phoenix default page. Open up web/router.ex (more or less analogous to Rails’ config/routes.rb):

defmodule Remynders . IndexView do use Remynders . Web , :view end

Finally, we have the template in web/templates/index.html.eex:

< div class = " headline " > Set Quick Reminders Quickly </ div > < a href = " # " class = " button " > Create a reminder </ a >

If you head over the root index now you’ll see a bit of our creation, but you’ll also notice two things:

Our creation currently looks like garbage. There’s a bunch of “Phoenix Framework” marketing material still left over on the page.

To solve those problems, we have to change the layout and some CSS.

Layouts

If you open web/templates/layout/application.html.eex, you’ll see the markup that’s dropping the Phoenix marketing material all over the place. Instead, we’ll replace it with our markup:

<!DOCTYPE html> < html lang = " en " > < head > < meta charset = " utf-8 " > < meta http-equiv = " X-UA-Compatible " content = " IE=edge " > < meta name = " viewport " content = " width=device-width, initial-scale=1 " > < meta name = " description " content = " " > < meta name = " author " content = " " > < title > Remynders </ title > <link rel="stylesheet" href="<%= static_path(@conn, "/css/app.css") %>"> </ head > < body > < div class = " page_wrapper " > < div id = " logo " > < h1 > Remynders </ h1 > </ div > < p class = " alert alert-info " role = " alert " > <%= get_flash(@conn, :info) %> </ p > < p class = " alert alert-danger " role = " alert " > <%= get_flash(@conn, :error) %> </ p > <%= @inner %> </ div > <script src="<%= static_path(@conn, "/js/app.js") %> " > </ script > < script > require ( "web/static/js/app" ) </ script > </ body > </ html >

The only part of this we need to be concerned with at the moment is , where our rendered templates will simply be “dropped in” (again, incredibly similar to the Rails concept of application.html.erb). So, we’ve solved part of our problem, but aesthetics aren’t the best quality of Remynders…yet.

Static Files

We want to modify the CSS for both the layout and for a given page. Giving the top of web/static/css/app.scss a quick glance shows us that Phoenix comes with a copy of Bootstrap ready to go. Since this is a small app and we don’t care too much about supporting a ton of different browsers with a complex style, we’ll just get rid of Bootstrap. We’ll replace app.css with:

body { font-family : "Helvetica Neue" , Helvetica , Arial , sans-serif ; margin : 0 ; padding : 0 ; border : none ; } #logo h1 { font-size : 20 px ; margin : auto ; text-align : center ; padding-bottom : 20 px ; color : #fff ; background-color : #cc0000 ; padding-top : 10 px ; margin-bottom : 40 px ; text-transform : uppercase ; letter-spacing : 2 px ; } .headline { font-weight : bold ; text-align : center ; font-size : 40 px ; } .button { display : inline-block ; border : 4 px solid #000 ; padding : 20 px ; color : #000 ; text-transform : uppercase ; font-weight : bold ; text-decoration : none ; font-size : 12 px ; letter-spacing : 1 px ; margin : 35 px ; } .button :hover { transition : background-color 0.3 s ease ; background-color : #cc0000 ; color : #fff ; border : 4 px solid #cc0000 ; } .center_block { margin : auto ; text-align : center ; }

That CSS makes the index page look a bit better. As is evident, the app/static directory holds the static elements of our web app (e.g. Javascript, CSS, etc.).

Helpers

Right now, our index page is more or less static. We want to link it up to a form that will let us a create a reminder. First of all, we need to fix up our routes so that we set up resource routing for a “Reminder” (exactly how we might in Rails):

resources "/reminders" , ReminderController

That sets up the resource routes, but we need a ReminderController before stuff will start working. Again, we create a new controller in web/controllers/reminder_controller.ex:

defmodule Remynders . ReminderController do use Remynders . Web , :controller plug :action def new ( conn , _params ) do render conn , "new.html" end end

Now, we’ll fix the link in the index page. First, use the URL helper in web/views/index_view.ex:

defmodule Remynders . IndexView do use Remynders . Web , :view alias Remynders . Router . Helpers def new_reminder_path do Helpers . reminder_path ( Remynders . Endpoint , :new ) end end

We can do that by opening up web/templates/index.html.eex and replacing:

< a href = " # " class = " button " > Create a reminder </ a >

with this:

< a href = " <%= new_reminder_path %> " class = " button " >

So, here’s what we’ve done. First of all, we added an alias in the view:

alias Remynders . Router . Helpers

That just lets us refer to Remynders.Router.Helpers as just Helpers . Purely for convenience. Then, we used the actual URL helper:

Helpers . reminder_path ( Remynders . Endpoint , :new )

Which defined that as a function within the view. This lets us call the function from the actual template to set up the link. All this seems really complicated compared to Rails’ link_to and it turns out that there’s another way. We mostly did this view function thing to demonstrate how we can call methods in the view from the template. We can actually replace our tag with an HTML helper:

< % = link "Create Reminder" , to : reminder_path ( @conn , :new ) , class : "button" % >

Now, if you head over to the index page and click on the button you will get…an error page. We haven’t set up the view yet!

Until Next Time

So far, it might seem like we haven’t come very far. We’ve only served some very simple pages through Phoenix and barely worked out the URL helper. But, we’ve set a firm foundation on which we can build quickly with form helpers, models, background processing and the HTML5 notifications API. We’ll be covering a lot of that in the next article!

Further Reading