Creates and upgrades Sig's database tables from your application's own migrations.

The migrations run on your application's repo, the same one Sig uses at runtime (see Sig.Repo).

Sig's tables are versioned. Generate a migration in your app:

mix ecto.gen.migration add_sig_tables

and call up/1 and down/1 from it:

defmodule MyApp.Repo.Migrations.AddSigTables do
  use Ecto.Migration

  def up, do: Sig.Migration.up(version: 1)

  # Passing version: 1 drops all of Sig's tables.
  def down, do: Sig.Migration.down(version: 1)
end

When a new version of Sig needs schema changes, its changelog will tell you the new version number. Create another migration that upgrades to it, and rolls back to the version you had before:

defmodule MyApp.Repo.Migrations.UpgradeSigTablesToV2 do
  use Ecto.Migration

  def up, do: Sig.Migration.up(version: 2)
  def down, do: Sig.Migration.down(version: 2)
end

Migrations are idempotent: up/1 only applies the versions that are not yet in the database, and down/1 only reverts the ones that are. The current version is stored as a comment on the workflows table.

Prefixes

Use the :prefix option to install the tables in a PostgreSQL schema other than public. The schema is created if it does not exist:

def up, do: Sig.Migration.up(version: 1, prefix: "sig")
def down, do: Sig.Migration.down(version: 1, prefix: "sig")

Then configure Sig to use the same prefix at runtime:

config :sig, repo: MyApp.Repo, prefix: "sig"