ElixirWeekly

Issue #202 - Using Mnesia in an Elixir Application

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

Here's what the latest issue looks like:

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

Phoenix LiveView: Multi-step Forms
Big forms are a pain to manage— even harder to manage when you need to change values based on previous input and compute data based on that new selection. David shows how Phoenix LiveView can make this easier.

Using Mnesia in an Elixir Application
Learn more about Mnesia, see when you would use such a tool, and take a look at some of the pros and cons of using it.

Let's Code: Contact Form in Phoenix
Zach's writing a series on adding a contact form to a Phoenix 1.4+ application. This post covers the schema his approachto data modeling in Phoenix applications that use Ecto.

Automate Your Elixir Deployments - Part 2 - Distillery & Edeliver
Dorian finishes his series on Automating Elixir Deployments with this article on using Distillery and eDeliver to build a release and push it to production.

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