Migrating on existing tenants in Production

[churcho]

How do you run migrations in production environments with no mix?

I made changes to some of my tables and would like to propagate this to already existing tenants.

Do we need to keep a table with existing [tenants]?(

triplex/lib/triplex/config.ex

Line 19 in f49c43f

tenant_table: :tenants

)

[kelvinst]

@churcho sorry it took so long, what do you mean? mix triplex.migrate should do that for your (running the migrations on all existing tenants). Please checkout the docs for it: https://hexdocs.pm/triplex/Mix.Tasks.Triplex.Migrate.html#content

[kelvinst]

If you use release though, that is a little bit trickier, but you can combine Triplex.all with Triplex.migrate and migrate all of the tenants on the database on your remote console.

[stueccles]

@kelvinst it would be nice if

Enum.each(Triplex.all, &Triplex.migrate(&1) end)

worked but alas it doesn't as Triplex.all returns a list of prefixes which Triplex.migrate then applies to_prefix on again...

it is not difficult to work around and running

Enum.each(Triplex.all, &Ecto.Migrator.run(
          My.Repo,
          Triplex.migrations_path(My.Repo),
          :up,
          all: true,
          prefix: &1
        ))

works in a production terminal to do the tenant migrations.

[kelvinst]

Yeah, we actually need to think of better ways of doing those. Maybe a `Triplex.migrate_all` function would make it easier, but we still have to come up with a better way to decide when to apply `to_prefix` and when not to apply it. I just can’t figure any way of doing that without breaking the API so hard that we would need to bump the version to 2.0. Best, Kelvin Stinghen kelvin.stinghen@me.com

…

On Sep 16, 2019, at 16:24, Stuart Eccles ***@***.***> wrote: @kelvinst <https://github.com/kelvinst> it would be nice if Enum.each(Triplex.all, &Triplex.migrate(&1) end) worked but alas it doesn't as Triplex.all returns a list of prefixes which Triplex.migrate then applies to_prefix on again... it is not difficult to work around and running Enum.each(Triplex.all, &Ecto.Migrator.run( My.Repo, Triplex.migrations_path(My.Repo), :up, all: true, prefix: &1 )) works in a production terminal to do the tenant migrations. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#66?email_source=notifications&email_token=AAVJUHKX5RZMWH5423G7P5TQJ7MOBA5CNFSM4G7OI6I2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD62HTJI#issuecomment-531921317>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAVJUHNQWSRYBT2ULXXOZRDQJ7MOBANCNFSM4G7OI6IQ>.

[kelvinst]

We’re open to suggestions though. Best, Kelvin Stinghen kelvin.stinghen@me.com

…

On Sep 16, 2019, at 16:55, Kelvin Stinghen ***@***.***> wrote: Yeah, we actually need to think of better ways of doing those. Maybe a `Triplex.migrate_all` function would make it easier, but we still have to come up with a better way to decide when to apply `to_prefix` and when not to apply it. I just can’t figure any way of doing that without breaking the API so hard that we would need to bump the version to 2.0. Best, Kelvin Stinghen ***@***.*** ***@***.***> > On Sep 16, 2019, at 16:24, Stuart Eccles ***@***.*** ***@***.***>> wrote: > > @kelvinst <https://github.com/kelvinst> it would be nice if > > Enum.each(Triplex.all, &Triplex.migrate(&1) end) > worked but alas it doesn't as Triplex.all returns a list of prefixes which Triplex.migrate then applies to_prefix on again... > > it is not difficult to work around and running > > Enum.each(Triplex.all, &Ecto.Migrator.run( > My.Repo, > Triplex.migrations_path(My.Repo), > :up, > all: true, > prefix: &1 > )) > works in a production terminal to do the tenant migrations. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub <#66?email_source=notifications&email_token=AAVJUHKX5RZMWH5423G7P5TQJ7MOBA5CNFSM4G7OI6I2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD62HTJI#issuecomment-531921317>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAVJUHNQWSRYBT2ULXXOZRDQJ7MOBANCNFSM4G7OI6IQ>. >

[kelvinst]

Anyway, we are currently working on a braking change that would force some people to add another lib to their projects if they want the plugs, so why not? 🤷‍♂