Digests » 76
DailyDrip is rebooting ElixirSips by building a production Phoenix-based Forum engine - Firestorm - and we're running a Kickstarter right now to help make it more awesome. In addition, we'll be producing a month of free daily content to take someone through the basics of Elixir, OTP, Ecto, and Phoenix as a thank you to all of our subscribers and backers.
This is the third post in a series on using Phoenix and GraphQL to create clean and powerful API’s. In this post I will cover adding authentication to our API with Guardian. For those who are just joining us, I recommend starting with the first post before starting this one. However, you can start where we left off last time by cloning the repo and checking out the checkpoint-2 branch. If you go that route you’ll want to run $ mix ecto.setup in order to create and populate your database (postgres) with some dummy data.
Of late, we have been porting one of our internal apps from Rails to Phoenix. We are using Capistrano for deploying Rails apps. We have Jenkins CI which listens to features merged into master, and uses Capistrano to deploy to production.
In the previous chapter we have learned about many_to_many associations and how to map external data to associated entries with the help of Ecto.Changeset.cast_assoc/3. While in the previous chapter we were able to follow the rules imposed by cast_assoc/3, doing so is not always possible nor desired.
As explained in this post, I made the switch from a slow Wordpress website to a blazing fast application built with Elixir and Phoenix. Now, I want to share the 10 things I learned about these technologies as a Rubyist.
An Elixir SDK for the Medium.com API.