Subscribe for only $15 to access all of our content
By default, Phoenix doesn’t precompile templates in nested directories. In this episode we’ll see how we can update Phoenix to let us use templates in nested directories.
In this episode we’ll take an existing Elixir Phoenix application and build an Atom feed for it. To build the feed we’ll use the Atomex package.
In the final part of this series we’ll use Phoenix Channels to improve the UI so that our coin tracker page updates automatically when a new cryptocurrency price is found.
In this episode we’ll build a chat application that has multiple chat rooms. The rooms will be created dynamically from the URL and will use Phoenix Channels to provide realtime functionality.
In this episode we’ll build a contact form for an existing Elixir Phoenix application. When a user submits the form, an email will be sent using the Bamboo library.
In part 4 of our Phoenix LiveView series we’ll use Phoenix Presence to track how many users are currently signed in to our application.
Often different layouts need to be rendered for different parts of a web application. In this episode we look at a few ways of doing this in Elixir.
Often you’ll have sensitive information that you don’t want to show up logs. In this episode we’ll see how to configure Phoenix to specify what parameters you want filtered in your logs.
In this episode we’ll explore one way to use Phoenix to create a nested form that saves an associated record in our database.
In part 3 of our series we’ll broadcast album changes to all clients using Phoenix.PubSub and Phoenix LiveView.
In part 2 we’ll use Phoenix LiveView event bindings to dynamically render a form and save changes to the database. Our form will be validated using a changesets coming from LiveView.
In part 1 we get started by installing Phoenix LiveView and setting it up to work with an existing Elixir Phoenix application. Then we’ll update a page to render data using LiveView.