Every Thursday: No frills, no click-through, no spam.
Here's what the latest issue looks like:
Welcome to Issue #188
I was overwhelmed by work and forgot to send out the newsletter yesterday.
This week in Elixir
Use Google, Github, Twitter, Facebook, or add your custom strategy for authorization to your Pow enabled Phoenix app.
Let It Rain - Ditch that Umbrella App!
A post about converting an umbrella app back to "standard layout". The author also issued a trigger warning: this post contains too many occurrences of the words “app,” “application,” “folder,” “directory,” etc.
Reusable Elixir Libraries
Chris wrote about one of the patterns he uses for making “stateful” libraries (libraries that provide processes, ets tables, etc.) more configurable and reusable. Very good read!
Skogsrå: Simplifying Your Elixir Configuration
Once an Elixir project is large enough, maintaining config files and config variables becomes a nightmare. This blog post shows the basics of using Skogsra to simplify your Elixir project’s configuration.
Phoenix Presence Inside LiveView |> A Simple Example
In this post of Real World Phoenix I discover how easy it can be to incorporate Phoenix Presence inside LiveView
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).