View Source Get Started with Ash and Phoenix


In this guide we will:

  1. Create a new Phoenix project
  2. Setup Ash, AshPhoenix and AshPostgres as dependencies
  3. Create a basic Blog.Post resource
  4. Create and migrate the database
  5. Learn how to interact with your resource
  6. Integrate a minimal Phoenix LiveView with Ash



If you want to follow along yourself, you will need the following things:

  1. Elixir (1.12 or later) and Erlang (22 or later) installed
  2. PostgreSQL installed
  3. A text editor
  4. A terminal to run the examples


Create a New Phoenix Project

Install Phoenix

This section is based on the Phoenix installation docs. For more details go there.

First we need to install the Phoenix project generator, then we'll run the generator to create our new project.

# install Phoenix project generator
$ mix archive.install hex phx_new

# generate Phoenix project
$ mix my_ash_phoenix_app

# cd into project
$ cd my_ash_phoenix_app

Don't run mix ecto.create

Do not run mix ecto.create, (as it asks you to) we will do this the Ash way later.

Add Dependencies

We now need to add Ash, AshPhoenix and AshPostgres to our Phoenix project. We need to add the dependencies to the deps function in our mix.exs. We'll also need to add dependencies to our .formatter.exs to ensure consistent formatting when using mix format.

# mix.exs

  def deps do
      # use `mix <library_name>` to get the latest versions of each dependency, for example, `mix phoenix`
      {:phoenix, "~> x.x"},
      # ...
      {:ash, "~> x.x"},
      {:ash_postgres, "~> x.x"},
      {:ash_phoenix, "~> x.x"}

Add :ash, :ash_phoenix, and :ash_postgres to your .formatter.exs file.

# .formatter.exs
  import_deps: [..., :ash, :ash_phoenix, :ash_postgres],

Now in the terminal install these new dependencies.

$ mix deps.get

Use AshPostgres.Repo

We need to swap Ecto.Repo for AshPostgres.Repo. AshPostgres.Repo enriches your repo with additional AshPostgres specific behaviour, but is essentially a thin wrapper around Ecto.Repo. To use AshPostgres.Repo change your repo module to look like this:

# lib/my_ash_phoenix_app/repo.ex

defmodule MyAshPhoenixApp.Repo do
  use AshPostgres.Repo, otp_app: :my_ash_phoenix_app

  # Installs extensions that ash commonly uses
  def installed_extensions do
    ["ash-functions", "uuid-ossp", "citext"]

Edit Config

We need to specify the Ash domains that our application uses.

Add this to your config:

# config/config.exs

import Config

config :my_ash_phoenix_app,
  ash_domains: [MyAshPhoenixApp.Blog]

Create the Domain and add Resources

An Ash domain can be thought of as a Bounded Context in Domain Driven Design terms and can seen as analogous to a Phoenix context. Put simply, its a way of grouping related resources together. In our case our domain will be called MyAshPhoenixApp.Blog.

An Ash domain points to Ash resources. An Ash domain can point to one or more resources. In our case we will only have a single resource MyAshPhoenixApp.Blog.Post. We'll be taking a deeper look into that in the next section.

For now take a look at the Blog domain and the associated resources:

# lib/my_ash_phoenix_app/blog/blog.ex

defmodule MyAshPhoenixApp.Blog do
  use Ash.Domain

  resources do
    resource MyAshPhoenixApp.Blog.Post do
      # Define an interface for calling resource actions.
      define :create_post, action: :create
      define :list_posts, action: :read
      define :update_post, action: :update
      define :destroy_post, action: :destroy
      define :get_post, args: [:id], action: :by_id

Creating Resources

Creating the Post Resource

A resource is a central concept in Ash. In short, a resource is a domain model object in your system. A resource defines the data it holds and defines the actions that can operate on that data.

When we create Post we will place it in lib/my_ash_phoenix_app/blog/post.ex. So the structure after making the resource should look like so:


Below is the resource module. Read the comments carefully, every line is explained:

# lib/my_ash_phoenix_app/blog/post.ex

defmodule MyAshPhoenixApp.Blog.Post do
  # Using Ash.Resource turns this module into an Ash resource.
  use Ash.Resource,
    # Tells Ash where the generated code interface belongs
    domain: MyAshPhoenixApp.Blog,
    # Tells Ash you want this resource to store its data in Postgres.
    data_layer: AshPostgres.DataLayer

  # The Postgres keyword is specific to the AshPostgres module.
  postgres do
    # Tells Postgres what to call the table
    table "posts"
    # Tells Ash how to interface with the Postgres table
    repo MyAshPhoenixApp.Repo

  actions do
    # Exposes default built in actions to manage the resource
    defaults [:read, :destroy]

    create :create do
      # accept title as input
      accept [:title]

    update :update do
      # accept content as input
      accept [:content]

    # Defines custom read action which fetches post by id.
    read :by_id do
      # This action has one argument :id of type :uuid
      argument :id, :uuid, allow_nil?: false
      # Tells us we expect this action to return a single result
      get? true
      # Filters the `:id` given in the argument
      # against the `id` of each element in the resource
      filter expr(id == ^arg(:id))

  # Attributes are simple pieces of data that exist in your resource
  attributes do
    # Add an autogenerated UUID primary key called `:id`.
    uuid_primary_key :id
    # Add a string type attribute called `:title`
    attribute :title, :string do
      # We don't want the title to ever be `nil`
      allow_nil? false

    # Add a string type attribute called `:content`
    # If allow_nil? is not specified, then content can be nil
    attribute :content, :string

Creating and Migrating the Database

We have specified the resource in Ash. But we have yet to create it in our data layer (in our case Postgres).

First we need to create our database:

$ mix ash.setup

Running setup for AshPostgres.DataLayer...
The database for MyAshPhoenixApp.Repo has been created

01:23:45.678 [info] Migrations already up

Now we need to populate our database. We do this by generating and performing a migration.

We can use a generator to produce a migration for us. Ash can deduce what needs to go into the migration and do the hard work for us, to do this use the command below:

$ mix ash.codegen initial_migration

# ... don't worry about other files it creates

Generating Migrations:
* creating priv/repo/migrations/20230208045101_initial_migration.exs

Here is the migration file commented in detail:

# priv/repo/migrations/20230208045101_initial_migration.exs

defmodule MyAshPhoenixApp.Repo.Migrations.InitialMigration do
  use Ecto.Migration

  # This function runs when migrating forward
  def up do
    # Creates the `:posts` table
    create table(:posts, primary_key: false) do
      # Adds primary key attribute `:id` of type `:uuid`
      # null values are not allowed
      add :id, :uuid, null: false, default: fragment("gen_random_uuid()"), primary_key: true

      # Adds attribute `:title` of type `:text`, null values are not allowed
      add :title, :text, null: false
      # Adds attribute `:content` of type `:text`, null values are allowed
      add :content, :text

  # This is the function that runs if you want to rollback the migration.
  def down do
    # Deletes the `:posts` table
    drop table(:posts)

We can run the up/0 function which will perform the desired operations on the Postgres database. We do this with the migrate command:

$ mix ash.migrate

In case you want to drop the database and start over again during development you can use mix ash.reset.

Interacting with your Resources

All interaction with your resource attributes always occur through an action. In our resource we are using the default actions for :create, :read, :update, :destroy along with a custom action :by_id.

:create and :update and :destroy actions require a changeset. Ash changesets are conceptually similar to Ecto changesets. They're data structures which represent an intended change to an Ash resource and provide validation.

The :read action takes a query instead of a changeset.

Below is the most verbose way of calling your resource. All other ways of interaction are some kind of shorthand of these. This means at some point a changeset is being created and passed to the domain, even if it's encapsulated within another function.

# create post
new_post =
  |> Ash.Changeset.for_create(:create, %{title: "hello world"})
  |> Ash.create!()

# read all posts
|> Ash.Query.for_read(:read)

# get single post by id
|> Ash.Query.for_read(:by_id, %{id:})
|> Ash.read_one!()

# update post
updated_post =
  |> Ash.Changeset.for_update(:update, %{content: "hello to you too!"})
  |> Ash.update!()

# delete post
|> Ash.Changeset.for_destroy(:destroy)
|> Ash.destroy!()

As stated above, this is verbose so Ash has a built in shortcut - The code_interface. You may notice this has already been done in your Post resource inside of the domain module.

you can call code interfaces whatever you like

The function name doesn't have to match the action name in any way. You could also write:

define :make_post, action: :create

That's perfectly valid and could be called via Blog.make_post/2.

Now we can call our resource like so:

# create post
new_post = MyAshPhoenixApp.Blog.create_post!(%{title: "hello world"})

# read post

# get post by id

# update post
updated_post = MyAshPhoenixApp.Blog.update_post!(new_post, %{content: "hello to you too!"})

# delete post

Now isn't that more convenient?

raising and non-raising functions

All functions that interact with an Ash resource have a raising and non-raising version. For example there are two create functions create/2 and create!/2. create/2 returns {:ok, resource} or {:error, reason}. create!/2 will return just the record on success and will raise an error on failure.

Connecting your Resource to a Phoenix LiveView

Now we know how to interact with our resource, let's connect it to a simple Phoenix LiveView. Here is the LiveView below. If you are using phoenix live_view <= 0.18, you will need to use let={} instead of :let={}.

# lib/my_ash_phoenix_app_web/posts_live.ex

defmodule MyAshPhoenixAppWeb.PostsLive do
  use MyAshPhoenixAppWeb, :live_view

  alias MyAshPhoenixApp.Blog
  alias MyAshPhoenixApp.Blog.Post

  def render(assigns) do
    <h2 class="text-xl text-center">Your Posts</h2>
    <div class="my-4">
      <div :if={Enum.empty?(@posts)} class="font-bold text-center">
        No posts created yet
      <ol class="list-decimal">
        <li :for={post <- @posts} class="mt-4">
          <div class="font-bold"><%= post.title %></div>
          <div><%= if Map.get(post, :content), do: post.content, else: "" %></div>
            class="mt-2 p-2 bg-black text-white rounded-md"
            Delete post
    <h2 class="mt-8 text-lg">Create Post</h2>
    <.form :let={f} for={@create_form} phx-submit="create_post">
      <.input type="text" field={f[:title]} placeholder="input title" />
      <.button class="mt-2" type="submit">Create</.button>
    <h2 class="mt-8 text-lg">Update Post</h2>
    <.form :let={f} for={@update_form} phx-submit="update_post">
      <.label>Post Name</.label>
      <.input type="select" field={f[:post_id]} options={@post_selector} />
      <.input type="text" field={f[:content]} placeholder="input content" />
      <.button class="mt-2" type="submit">Update</.button>

  def mount(_params, _session, socket) do
    posts = Blog.list_posts!()

    socket =
        posts: posts,
        post_selector: post_selector(posts),
        create_form: AshPhoenix.Form.for_create(Post, :create) |> to_form(),
        update_form: AshPhoenix.Form.for_update(List.first(posts, %Post{}), :update) |> to_form()

    {:ok, socket}

  def handle_event("delete_post", %{"post-id" => post_id}, socket) do
    post_id |> Blog.get_post!() |> Blog.destroy_post!()
    posts = Blog.list_posts!()

    {:noreply, assign(socket, posts: posts, post_selector: post_selector(posts))}

  def handle_event("create_post", %{"form" => %{"title" => title}}, socket) do
    Blog.create_post(%{title: title})
    posts = Blog.list_posts!()

    {:noreply, assign(socket, posts: posts, post_selector: post_selector(posts))}

  def handle_event("update_post", %{"form" => form_params}, socket) do
    %{"post_id" => post_id, "content" => content} = form_params

    post_id |> Blog.get_post!() |> Blog.update_post!(%{content: content})
    posts = Blog.list_posts!()

    {:noreply, assign(socket, posts: posts, post_selector: post_selector(posts))}

  defp post_selector(posts) do
    for post <- posts do

Don't forget to add the LiveView to your router.

# lib/my_ash_phoenix_app_web/router.ex
  scope "/", MyAshPhoenixAppWeb do
    # ...
    live "/posts", PostsLive

Now, start the web server by running mix phx.server. Then, visit http://localhost:4000/posts in your browser to see what we have just created.

You can see how using functions created by our code_interface makes it easy to integrate Ash with Phoenix.

You may also notice this is the first time we've used the AshPhoenix library. The AshPhoenix library contains utilities to help Ash integrate with Phoenix and LiveView Seamlessly. One of these utilities is AshPhoenix.Form which can automatically produce changesets to be used in the forms.

That's it for this guide. We've gone from 0 to a fully working Phoenix App using Ash. To get a closer look, see the accompanying repo here.

Where to Next?

We are really just scratching the surface of what can be done in Ash. Look below for what to look at next.

Continue Learning

There's a few places you can go to learn more about how to use ash:

Ash Authentication & Ash Authentication Phoenix

See the power Ash can bring to your web app or API. Get authentication working in minutes.

Add an API (or two)

Check out the AshJsonApi and AshGraphql extensions to effortlessly build APIs around your resources.