ElixirWeekly

Issue #329 - Get Started With Rayex (Raylib for Elixir)

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

Here's what the latest issue looks like:

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

Upgrading to Phoenix 1.7
To celebrate the first release of Phoenix 1.7, let's use Chris McCord’s upgrade guide to take an existing application to Phoenix 1.7.

Get Started With Rayex (Raylib for Elixir)
Andrew wrote this blog post for getting started with Raylib, the Elixir implementation of the Raylib game library. So cool!

Elixir, OpenTelemetry, and the Infamous N+1
Alex wrote this OpenTelemetry article for Phoenix projects with an awesome demo repo that visualizes telemetry events with Grafana!

Simulate Latency, Jitter, and Package Loss in Phoenix LiveView
Peter shows us how to make your LiveView app resilient against bad internet connections by simulating latency, jitter, and package loss when developing locally.

Elixir Code Security: Prioritize Security in Your CI With 4 Tools
The fine folks of Semaphore CI describe how to improve your code security and dependency checking by getting warnings about attack vectors in an automated and actionable way.

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