agentleFS
ychabychab/museflow/migrations/AGENTS.md

museflow / migrations

AGENTS.md1 starsChanged 17 days agoMITView on GitHub

While this file exists, MuseFlow is in development: no server runs in production, so the schema changes without migrations. When that ends, this file is deleted and schema changes become ordinary Alembic revisions. - Never add a revision. versions/initial.py is the only one, regenerated by Alembic at each schema change. Never edit it by hand, and never write a data patch or a backfill_* method: a reset empties the database, the imports or a new computation fill it again. -…

The file

Files
AGENTS.md

Schema changes

While this file exists, MuseFlow is in development: no server runs in production, so the schema changes without migrations. When that ends, this file is deleted and schema changes become ordinary Alembic revisions.

  • Never add a revision. versions/initial.py is the only one, regenerated by Alembic at each schema change. Never edit it by hand, and never write a data patch or a backfill_* method: a reset empties the database, the imports or a new computation fill it again.
  • A schema change resets the database, without losing what was paid for (LLM results) or typed by the user (ratings, blacklist):
    1. make backup-export, before changing the models: the exports read the current schema. It also writes a full SQL dump, the way back with the current code (make db-restore).
    2. Change the models, delete versions/initial.py, make reset && make up, make db-revision, then rename the generated file to initial.py.
    3. museflow users create, make backup-import (migrations, history, then the exports), museflow provider connect.
  • The reset is the user's call. make backup-export is free and read-only; make reset destroys the local database: ask before running it.
  • Data a reset still loses (anything without an export/import, e.g. the saved playlists) is named in the PR; a new table worth keeping gets its export/import, chained in backup-export / backup-import.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.