ElixirWeekly
Every Thursday: No frills, no click-through, no spam.
Here's what the latest issue looks like:
Welcome to Issue #156
It's Issue #156 already, which means that ElixirWeekly is now 3 years old.
Oh wow. The ecosystem has matured a lot since early July 2016, when this little newsletter started.
Time flies.
This week in Elixir
Health Checks for Plug and Phoenix
Johanna shares a simple pattern for setting up HTTP based health checks for Plug/Phoenix applications.
Scenic - Getting Started from Scratch
Lars created this guide on how to get started with the Scenic UI framework. More specifically it also covers adding Scenic to an existing project in some detail.
Refactoring Phoenix Controllers
Hubert wrote a blog post explaining several techniques I often use to refactor Phoenix controller.
Distributing Phoenix -- Part 2
A follow on from setting up a distributed Phoenix application in Part 1, in this article Erik covers creating the business logic, and ensuring the data is distributed across the cluster using Horde and DeltaCrdt.
Events and Various Kinds of Coupling
Maciej wrote this short piece about different kinds of coupling and their relation to events.
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).
