Issue #20: Turbolinks with Phoenix, Binary Data over Sockets and How Supervisors Work

Every Thursday: No frills, no click-through, no spam.

Here's what the latest issue looks like:

This week in Elixir

Does your team use Credo?
Hi, @rrrene here! I will be giving a Elixir talk in Hamburg next week, which includes a deeper look at Credo. Now I am looking for companies using Elixir and Credo for their projects (for a “brag slide”). Tweet me!

Why We Chose Turbolinks
Changelog actively chose Turbolinks for their new custom-made CMS, installed it, and integrated it into their application. It is pretty interesting to read their reasoning.

Elixir, Ruby, don’t fight. Talk.
A series of posts, explaining how to talk from Elixir to Ruby, and vice versa.

Real Responses from Mock Modules
After writing about how to move a mock module out of your production code and into your test folder, @philosodad is showing us how to use the mock HTTP module in testing.

How Supervisors Work
In Erlang (and Elixir) supervisors are processes which manage child processes and restart them when they crash. This post takes a look at the details of how supervisors are implemented.

Binary data over Phoenix sockets
This post explains how to send raw binary data through Phoenix channels using the MessagePack format to deliver the payload.

Community Corner Help wanted

doomspork/elixir-school: Update the `basics/pattern-matching` lesson

In this section, I want to highlight projects that are looking for contributors. To add your project to this section, just press reply!
That's it for this round, have a great day!
@rrrene from ElixirWeekly

If you like this newsletter, please tell the world!

You can view this issue in your web browser.

You can subscribe below:

Questions & Answers

Can I submit things I made to be included in the next issue?

Yes! Simply post them to ElixirStatus and you can be sure that they land on my radar.

Is my email address safe with you?

Yes. I'd like to consider myself a trustworthy individual, but then who doesn't?

I am, however, an active member of the open-source Elixir community and the maintainer of Credo and ElixirStatus. I will NOT ruin my reputation by selling your data to a third party.

Why do you require me to confirm my email address?

I just believe that requiring double opt-in to subscribe to any email-based system is a win for both parties: You are safe from unintentionally subscribing and I can be confident that you actually own the email address and want to receive the newsletter I send you :)


Feedback? Questions? Anything else?

Please contact René Föhring (email or tweet @rrrene for a quick conversation).