Digests » 125
This is a code-reading and exploration post about the WebSockets side of Phoenix. It builds upon some of the tracing techniques showcased in the previous post, to observe some of the internals of Phoenix. It also features some tricks I commonly employ to debug WebSocket related issues. The title and nature of this post are inspired by the marvellous book Ruby Under a Microscope written by Pat Shaughenessy.
Let’s talk a little bit more about Maps. I’ve already covered basics in the one of my previous articles. Now it is time to go deeper and discover how we can update Maps and add new items to it.
I just started using Gigalixir to host a web application I’m writing in Elixir. I already use Travis CI to run tests via GitHub, so one of the things I wanted to investigate was how to deploy my application to Gigalixir from Travis after tests pass.
Elixir, as a functional programming language, normally follows declarative programming paradigm instead of imperative. By defining lots of small independent functions and use some tools Elixir provides us, we will use less of control flow constructions comparing to other languages. Well, maybe comparing to imperative languages.
A post about what supervisors do, and how to build your own example supervisor that can restart dying processes.