komrad migrate
Apply any pending database migrations
komrad migrateApply any pending database migrations, connecting as the login that owns the schema.
The server never migrates: an engine connects as a login that cannot change the schema, and it refuses to start against a database missing migrations its build carries. So every upgrade runs this first, with owner_database_url (or KOMRAD_OWNER_DATABASE_URL) naming the owner, which falls back to database_url on a database no engine has joined.
While owner_database_url names the embedded Postgres, this creates it when there is none and starts it when it is down.
It refuses while another komrad is connected and the build holds migrations the database has not seen, since a change it makes could break them. It is safe to run against a database that is already current; it says so and exits zero.