A tutorial to understand how Phoenix, Umbrella, Distillery and Docker fit together.
What exactly happens when `GenServer.call/3` times out? Let's find out.
How to serve https from a simple Elixir app running locally with Cowboy in development mode
On occasion your Elixir is going to want to interact with an external program. This may be for speed, but more likely you are going to want to take advantage of a library that has been written in C. The most common options are using Ports and Native Interface Functions (NIFs).
For various reasons, may people are not fond of GenEvent. Here are some examples of using some good alternatives for broadcasting and subscribing to types of event: gproc, Phoenix PubSub, and the new process registry to be included in Elixir 1.4.
Elixir Nerves is awesome, but it make it awkward to test your code on your development computer - especially if it is not Linux. Here I explain how to overcome that hurdle.
Using Ecto without Phoenix is a bit fiddly to set up. This is a step-by-step tutorial to getting through that.
In Part 11, we looked at how to fetch our initial seat data via Phoenix channels. Our application, when it loads, opens a web socket to the server and then gets the initial seat data over this connection. Now we want to take a look at how to send and receive data over that channel in response to user interaction with the site.
Since the last post we have seen updates to both Elixir and Phoenix. Furthermore, as of Phoenix version 1.1.2, the version of Brunch that is used has been upgrade to ^2.1.1. This means that we will end up upgrading Brunch to version 2.1.3 or later, which affects the elm-brunch package that we use to build our Elm project.
We took a look, in Part 9, at how to fetch our initial seat data via an HTTP request. However, one of the most compelling reasons to use Phoenix is because of it's first class support for Channels.