tern VS postgresql-migrations

We have a repo with migrations written in SQL, and we use tern[1] to apply them.

[1]: https://github.com/jackc/tern

If you are using postgres and pgx you may want to use tern.

Recently i started using turn its more fun (IMPO) compared to others tool available https://github.com/jackc/tern

We use https://github.com/jackc/tern library (from the author of the pgx driver). We run migrations in k8s init containers and we do not do rollbacks (only up). Advantages over other popular solutions are:

I’ve been happy with https://github.com/jackc/tern .

I use tern for migrations. It’s from the same Author as pgx so everything in that ecosystem plays well.

Now my next issue is I'm trying to install tern using the "go versions 1.17 and higher" instructions in the docs here https://github.com/jackc/tern

I use https://github.com/jackc/tern + .env files which interpolate with its config for various environments.

Tern is a great language and framework agnostic solution for SQL migrations https://github.com/jackc/tern

I wrote my own simple solution, and I (and some others) have used it with some success in a few commercial projects. https://github.com/purcell/postgresql-migrations