Add new migrations framework

[ryanrhughes]

Having been burned a few times by migration runs, usually due to me pulling on my own during doing some development, I figured it was time to give a go at a revised migration framework that was a little more resilient than just comparing when we last pulled the repo vs today.

This updated framework seeks to be basically a direct ripoff of what Rails does, and has served us well there for years. A small log is kept at ~/.local/share/omarchy/migration.log (.gitignored) that stores the timestamps of any successful migration runs.

The migrations are ran normally via omarchy-update as they were before but could also be accessed directly via omarchy migrate.

There is also a migrations menu added to the omarchy TUI to allow access to these functions, though we may want to tuck those away in a deeper menu or only have it available on the CLI. While all of these screenshots are from the TUI, both call the same logic.

View Screenshots

Command

Tui

Status

List

Create

Run migrations (normal)

Run migrations (continue on failure prompt)

Re-run migration

[ryanrhughes]

Out of morbid curiosity, I explored what revisions would be required to store in a sqlite db vs log file. It was surprisingly little. ryanrhughes/omarchy@add-new-migrations-framework...ryanrhughes:omarchy:add-new-migrationa-framework-sqlite