ElixirWeekly

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

Here's what the latest issue looks like:

Issue #102

Welcome to Issue #102

Since I am currently on a kind of, sort of vacation-like travel thing, I will just include the stories posted on ElixirStatus.com below.

We'll be back to our regular scheduling next week!

This week in Elixir

7 Tips for Building Kiosk Devices with Nerves and Buildroot
Just a few things Michał has learned working with Elixir Nerves.

Typed Elixir Structs Without Boilerplate Code
Jean-Philippe has written a library to help you define structs with a type, default values and enforced keys, all thanks to an Ecto-like API.

Elixir API and Elm SPA - Part 2: Adding Guardian Authentication
This is part 2 of Miguel's series on building a CRUD app with Elixir as the JSON REST API and Elm as the SPA.

ZTD: Real-time Todo App over RabbitMQ
This is an Todo app example in Elixir/Phoenix that can synchronize with other running instances in real-time over RabbitMQ.

The anatomy of code documentation
While this was not written for Elixir, the underlying principles apply just as much.

Even more from around the Elixir community

Lesson 1: The Guessing Game (Elixir 1.6) Video

First Impression of Elixir, from a Rubyist’s Perspective Blog post

Part #5 of Building a Weather Station Using Elixir and Nerves is Live! Blog post

Quick Look at new :gen_server handle_continue Callback Blog post

How to Manage Ginormous ExVCR Cassettes Blog post

Submit your blog post/project update

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 :)

Contact

Feedback? Questions? Anything else?

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

ElixirWeekly by @elixirstatus

ElixirWeekly

Questions & Answers

Contact