Subscribe for only $15 to access all of our content
In this episode we'll look at how we can use a GenServer to schedule some recurring work. We'll create a GenServer fetches the price of a Bitcoin at a regular interval.
Now that we’ve created our ‘Order History’ pages, we need to make sure only the respective customers are able to view their order history. We’ll use Plug to help us do this.
In this episode we’ll build on the foundation we setup in part 1. We’ll populate our ‘order history’ and ‘receipt’ pages with actual data and make them accessible to our customers.
In this episode we get started building an order history page. We’ll look at how our application is structured, how we can fetch data from an API to build our receipts, and how to structure that data.
In this episode we’ll learn how to identify security issues in Phoenix applications. We’ll be using Sobelow to help us identify different potential vulnerabilities.
In this episode we’ll learn how to parse HTML with the Floki package. Floki makes it easy to search for specific nodes in HTML using CSS selectors.
Assigns allow you to set and access shared data in different contexts within Phoenix. In this episode we’ll explore how to use assigns in the connection, template, and socket.
In this episode we’ll learn how we can use feature flags to toggle different features of an application to different users. To do this we’ll be using the FunWithFlags package in an existing Elixir application.
In this episode we’ll look at how we can use the Phoenix router to define routes for our application. We’ll learn how to define single routes and full RESTful resources in Phoenix.
In this episode we’ll update an existing Elixir application to make it use a Stream throughout. Then we’ll see how we can use Task.async_stream to make concurrent API calls.
In this episode we’ll learn the basics of working with CSV files in Elixir. We’ll parse and existing CSV to get specific data from it. We’ll also learn how to build a new CSV file.
In this episode we’ll learn how to seed our Ecto database with some dummy info for use in a Phoenix application.