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 #167
This week in Elixir

Ruby vs Elixir. Which one do you Need for Your Software Project?
Interesting post for those trying to convince their boss of using Elixir.

How to Find an Elixir Job?
Interesting post for those looking for a job.

Up And Running With Faktory In Elixir
This post covers how to get an Elixir application set up with Faktory to allow users to process jobs in the background of their applications and take full advantage of the many features Faktory has on offer.

Running a Gatsby Blog Inside a Phoenix App
A simple guide on running a Gatsby blog inside a Phoenix app.

edisonywh/gearbox
Gearbox focuses on doing one thing and doing one thing right – state transitions. No surprise callbacks, no process management overhead, just pure functional state transitions.

Prometheus, PostGIS and Phoenix Part 2
In the final part of this series, Alex wraps up the Prometheus monitoring stack, writes a stress tester with Erlang’s httpc, and makes the Grafana dashboards dance!

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