How to disable ecto migration entirely for a repo app under umbrella?
Just do not create migrations.
yes, and the “priv/repo/migrations” folder need to be present
remove Phoenix.Ecto.CheckRepoStatus in dev mode
When developing agains a read-only legacy database Phoenix gives an error message on every web request that the schema_migrations table does not exist , even when not using migrations at all. Since it is a read-only database this schema_migrations table can of course not be created, unless you would use a second alternative database where you do have write rights to create this table.
The best solution for me in this case was indeed commenting out the Phoenix.Ecto.CheckRepoStatus plug in your endpoint.ex.
1 Like
Well versed. Thanks for elaborating man!
