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

Here's what the latest issue looks like:

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

This is an Elixir starter template for the Advent of Code challenges. It includes tests for each day, a mix task to run each part, and the ability to benchmark your solutions using Benchee.

The Big Elixir Talks Are Up
All 12 of the talks at The Big Elixir are now up on YouTube!

Phoenixcasts is a platform which aims to help newcomers and experienced developers alike learn web development using Elixir and Phoenix.

An Ueberauth Oauth 2 Walkthrough
This hows you how to set up 3rd party Oauth so your users can log in with Google, Facebook, Twitter, Slack, GitHub or other services using Uberauth!

How to Generate a Pid-File for an Elixir App
Neither plain mix applications nor Phoenix apps generate Pid-Files by default, but there’s a great drop-in solution in the form of a library called pid_file. This is a quick tutorial and screencast that covers setting it up.

How to Compose Queries in Ecto
Writing composable queries in Ecto including how to safely build queries that need to join through tables.

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


Feedback? Questions? Anything else?

Please contact René Föhring (email or tweet @rrrene for a quick conversation).