1) quite, yes. And I'm totally unfamiliar with it. 2) Well, yes. I'd like to at least provide SQLite so that invidious doesn't need a heavy DB (for personal use, e.g)

In reply to @farmerman:matrix.org
TheFrenchGhosty: do you recommend any of the instances?

In reply to @thefrenchghosty:pussthecat.org
Samantaz Fox: Honest question: what's the point of using a migration framework?

In reply to @samantazfox:pussthecat.org
being able to change the DB layout without requiring the maintainers to keep track of what changed and manually apply the migrations

In reply to @kavin1337:matrix.org
When you make changes to the database structure, you want to be able to upgrade them automatically instead of manual interventions

In reply to @farmerman:matrix.org
TheFrenchGhosty: Does geographic distance influence it in any way?

TheFrenchGhosty no, it doesn't. it simply allows to use something else than kemal as the DB owner

And check_tables on verifies that a table exists. if it doesn't => run SQL file. if it does => NOP.

In reply to @samantazfox:pussthecat.org

https://github.com/iv-org/invidious/issues/2620

I did read it more: honestly, we should just use the one that goes with the web framework we'll use: Lucky or Amber.

I'm against forking mg, we have enough things to take care of

I'm more in favor of micrate, tbh.

In reply to @samantazfox:pussthecat.org

I'm more in favor of micrate, tbh.

I don't care, micrate doesn't depend on amber

it's independant

As I said, it's a good dozen deps

In reply to @samantazfox:pussthecat.org
yep.

If not: Do we really want Lucky+Micrate

I edited