ElixirWeekly

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

Here's what the latest issue looks like:

Issue #400

Welcome to Issue #400

400 issues of ElixirWeekly published, in roughly 8 years.

It is amazing to see how there are ups and downs of publishing activity, with some weeks being rather light on material and then others bursting with innovations, exemplifying the slow-and-steady upwards trend of Elixir and its community.

Just wow. Time flies 🙂

This week in Elixir

Livebook: Elixir's Swiss Army Knife
Andrés writes about his "LiveView journey" from learning, to prototyping, to production.

Clustering Elixir From Laptop to Cloud
Mark from Fly.io shows us how to cluster the Elixir app running on your laptop to an Elixir app running in the cloud!

Your First LiveView!
Lubien wanted to give beginners an alternate path on getting started with LiveView that didn’t need a lot of setup.

Even more from around the Elixir community

Thinking Elixir: Migrating from Next.js to Phoenix Podcast

Elixir Streams |> ♻️ Refactoring Complex `else` Clauses in `with` (an Anti-pattern) Video

Survey on Refactoring for Elixir Video

Fabulous Speaker Line Up at GigCityElixir 2024! Conference

Mastering GenServer for Enhanced Elixir Applications | Curiosum Blog post

Optimum Elixir CI with GitHub Actions Blog post

Easy Empty States for Phoenix LiveView Streams Using Tailwind Blog post

Content Security Policy Header with Phoenix LiveView Blog post

Clivern/Lynx: 🐺 A Fast, Secure and Reliable Terraform Backend, Set up in Minutes. Project update

fuelen/seed_factory: A Toolkit for Test Data Generation Project update

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

ElixirWeekly by @elixirstatus

ElixirWeekly

Questions & Answers

Contact