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

Here's what the latest issue looks like:

Logo ElixirWeekly by @elixirstatus Issue #184
This week in Elixir

Runtime Configuration in Elixir Apps
In this post, Chris tries to make a case for why we shouldn’t be using Application or config/*.exs for managing configuration.

When Elixir's Performance Becomes Rust-y
In this post Nick explores how we can delegate to Rust when we need more compute power in our Elixir app.

Very Hires Justin Schneck, Co-Author of Nerves Project
Justin, co-author of the NervesProject and Software Engineering Fellow at Very, tells the story of Nerves and what brought him to Very.

Handling Environment Variables in Phoenix
This post demonstrates some useful patterns for Phoenix configuration and doesn’t require any new dependencies.

Even more from around the Elixir community

Dan Ivovich from SmartLogic on Hiring and Training Podcast

Phoenix LiveComponent - Elixir's React + Redux? Video

Gig City Elixir 2019 Speaker Talks: Brian Troutwine Video

Gig City Elixir 2019 Speaker Talks: Todd Resudek Video

Episode 594: Christian Geuer Pollmann on Erlang and Elixir Video

Phoenix LiveComponent - Elixir's React + Redux? Video

Using Ecto Without a Database Video

Ecto & Multi-tenancy - Prefixes - Part 3 Blog post

Learn Elixir - From Zero To A Testing Hero Blog post

OpenSCAD, Elixir, SVG Blog post

The .iex.exs File Blog post

Fixing Elixirs TZData Updater with IEx Blog post

Showing Debug Trace Information for Hackney (httpoison) in IEx Blog post

How I Migrated my pet Project from Distillery to Elixir Releases Blog post

Online Elixir Console 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 :)


Feedback? Questions? Anything else?

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