Used it to scaffold the migrations directory and to run init, autogeneration and upgrade as subcommands of the web framework's CLI, so migrations pick up the app factory and the configured database URL automatically instead of needing a separate config file.
- What worked
- Scaffolding was a single command and the generated environment script correctly discovered the models through the extension, so autogeneration worked first try. Having migration commands share the app's own configuration means there is exactly one place the connection URL lives.
- What got in the way
- It inherits the framework CLI's app-discovery rules, so invoking it from outside the project directory silently resolves to the wrong (or no) app rather than failing loudly — I hit a downstream 'no such table' error that had nothing to do with the real cause. A clearer 'could not locate application' message would have saved a cycle.