Book Image

Phoenix Web Development

By : Brandon Richey
Book Image

Phoenix Web Development

By: Brandon Richey

Overview of this book

Phoenix is a modern web development framework that is used to build API’s and web applications. It is built on Elixir and runs on Erlang VM which makes it much faster than other options. With Elixir and Phoenix, you build your application the right way, ready to scale and ready for the increasing demands of real-time web applications. This book covers the basics of the Phoenix web framework, showing you how to build a community voting application, and is divided into three parts. In the first part, you will be introduced to Phoenix and Elixir and understand the core terminologies that are used to describe them. You will also learn to build controller pages, store and retrieve data, add users to your app pages and protect your database. In the second section you will be able to reinforce your knowledge of architecting real time applications in phoenix and not only debug these applications but also diagnose issues in them. In the third and final section you will have the complete understanding of deploying and running the phoenix application and should be comfortable to make your first application release By the end of this book, you'll have a strong grasp of all of the core fundamentals of the Phoenix framework, and will have built a full production-ready web application from scratch.
Table of Contents (14 chapters)
4
Introducing User Accounts and Sessions

Summary

We’re now at a point where we have a good baseline to work from for our Poll Controller, which means we're also at a point where we can start transitioning from here into the work for our data side of things. In the next chapter, we’ll start diving into Contexts and Schemas and try to get a good working understanding of integrating a data model into our Phoenix application (and a lot of the design decisions that influence the current structure and why those decisions were made)!

So, now that we know how to glue together the different parts of our application and we understand a few of the pieces that are getting assembled, we need to explore what is arguably one of the largest and more complex pieces of the request/response puzzle: the database! We'll take a deep dive into Ecto and, of course, write good tests to cover any new code we write!

...