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:

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

Managing Distributed State with GenServers in Phoenix and Elixir
Pulkit explores working with Phoenix in a distributed setup.

Beacon CMS v0.1 and the Future
Leandro shares more about Beacon, a Phoenix LiveView-based CMS, and its future.

Build a Static Site in Elixir Under 5 Minutes with Phoenix Components
Shahryar shows how to quickly build a static blog site using Elixir and Phoenix components.

Elixir Clustering on a Kamal+Hetzner Deployment
Samrat has been experimenting with Kamal for deploying an Elixir application to Hetzner servers.

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