ElixirWeekly

Issue #153 - Enforcing Code Quality in Elixir

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

Here's what the latest issue looks like:

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

Real World Phoenix |> Let's Auth Some Users
Tjaco explores if there is a library in Elixir/Phoenix land to get user authentication up-and-running easily, while still keeping the Elixir mindset.

Enforcing Code Quality in Elixir
Enforcing your Elixir code to be well formatted, with no warnings and hopefully free of bugs. A mix alias to automate code quality.

How I Deploy (Phoenix apps)
I did some listener Q&A - the biggest question was if it’s hard to deploy Elixir apps, so I went through an example of how my site is deployed. How I deploy

Credo v1.1.0 released (Credo Plugins are here!)
Credo, the static code analysis tool emphasizing code consistency and teaching, finally got plugin support.

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