ElixirWeekly

Get your Elixir News in a weekly email!

Elixir is one of the most vibrant eco-systems in programming right now. There's so much happening and our community is growing faster and faster every day.

ElixirWeekly means: stuff you easily miss, shared on ElixirStatus and the web, handpicked articles and community news in one nice weekly email.

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

Here's what the latest issue looks like:

ElixirWeekly by @elixirstatus

Issue #459

Welcome to Issue #459

Greetings! A rather short issue this week, probably because everybody is getting ready for ElixirConf EU 💜

Also, next week there won't be an issue, as I need to take a week off ✌

This week in Elixir

Migrate to Phoenix 1.8 (rc Version) Guide
Mạnh tried Phoenix 1.8's release candidate and it’s an amazing update.

An Introduction to Ecto for Elixir Monitoring with AppSignal
In this post, Aestimo sets up Ecto monitoring in an Elixir application using AppSignal.

Even more from around the Elixir community

Thinking Elixir: Tidewave Triumphs and App Store Rebellions Video

ElixirConf EU 2025 on 15-16 May, Kraków & Virtual Conference

Contributing to Elixir Documentation: A Step-by-Step Guide Blog post

Announcing the EEF 2025 Board Election Candidates Blog post

What’s New in LiveDebugger v0.2.0? 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).