.github/workflows/protect_migrations.ymlname: Protect Migration Files on: pull_request: types: [opened, synchronize, reopened] branches: - main paths: - "priv/repo/migrations/**" - "priv/app_repo/migrations/**" jobs: check_migrations: runs-on: ubuntu-latest steps: - name: Checkout code uses: actions/checkout@v4 with: fetch-depth: 0 - name: Check for migration file changes run: | # Check for modified, deleted, or renamed migrations CHANGED_FILES=$(git

After a hardware failure on Fly.io triggered a migration to new hardware, I encountered an issue where the new machine didn't mount to the old volume but instead created a new one. Despite attempts to mount the old volume, persistent errors prevented me from attaching it to the application. This

I had to make a new blog because we can't have nice things.