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

Solidifying the new user experience

As mentioned previously, we'll want to do a bit more to really make our application production ready. Typically, when people think of something being production ready, they tend to associate that term and idea around hardening the product: making it more secure, making it perform better, cleaning up old spaghetti code, or other types of cleanup and polishing work. That's a very important thing to do as part of getting your application ready to live in a production environment, to be sure, but it's also not the whole thing. We'll start off by cleaning up some more of our application's layout and navigation issues, and then we'll move from there into cleaning up the user signup page (since we'll need to clean it up from our current default and boring design) to allow users to sign up via some OAuth provider.

...