It sounds like you might want to write a module.

https://github.com/duct-framework/core/#modules

Though modules are pure, so you’d need to combine that with something side-effectful.

Actually… wait, ignore all that 🙂

Yes, so the :migrations key in migrator.ragtime is just a vector, so you can supply it with a reference that produces a vector of migrations when it’s initiated.

So all you need is to write a ig/init-key method that returns a vector of Ragtime migrations.

thx.. just reading the docs..

this seems to be everyting needed...

couldn't find that part about modules, was looking in integrant docs...

I don’t think you don’t need a module for this. I’d forgotten that I was already thinking about this problem when I wrote the ragtime migrator to begin with.

You just need a key that returns an ordered collection of Ragtime migrations when initiated.

It might be helpfull to look into https://github.com/mariusz-jachimowicz-83/duct-migrations-auto-cfg