Drill
Seed data handling for Elixir
Drill is an elixir seeder library inspired by Seed Fu and Phinx.
Usage
-
Create your seeder modules. The directory where the seeder modules are located
does not matter as long as it has
use Drill, ....
In my_app/lib/seeds/user.ex:
defmodule MyApp.Seeds.User do
use Drill, key: :users, source: MyApp.Accounts.User
def run(_context) do
[
%{
email: "user1@example.com",
first_name: "John",
last_name: "Smith"
},
...
]
end
end
In my_app/lib/seeds/post.ex:
defmodule MyApp.Seeds.Post do
use Drill, key: :posts, source: MyApp.Blogs.Post
def deps do
[MyApp.Seeds.User]
end
def run(%Drill.Context{seeds: %{users: [user1, user2, user3 | _]}}) do
[
%{
content: Lorem.paragraph(),
user_id: user1.id
},
...
]
end
end-
Configure drill by adding the name of your application. This will let drill know which application
contains the seeder modules.
In
my_app/config/config.exs:
config :drill, :otp_app, :my_app-
Run
mix drill --r MyApp.Repoin the terminal with your project root as the current working directory
Installation
Drill is available on Hex.
To add it to a mix project, just add a line like this in your deps function in mix.exs:
def deps do
[
{:drill, "~> 0.1", only: [:dev, :test]},
]
enduse Drill options
source- source is the schema modulekey- once the seeder module runs, the inserted result will be saved to%Drill.Context{}.seeds[key]. Drill.Context struct is passed to one of Drill's callback which isrun/1to be discussed in theCallbacksection below.
Callbacks
constraints/0(optional) - returns a list of column names to verify for conflicts. If a conflict occurs all fields will just be updated. This prevents insertion of new records based on the constraints when drill is run again.deps/0(optional) - returns a list of seeder modules that should be run prior to the current seederrun/1(required) - returns a list of maps which keys are fields of the:sourceschema. Autogenerated fields such as:inserted_ator:updated_atmay not be defined. The first argument is theDrill.Contextstruct, which you can use to get the inserted records from previously run seeder modules (see Usage section above).
Documentation can be generated with ExDoc and published on HexDocs. Once published, the docs can be found at https://hexdocs.pm/drill.