Migrations create in a resources/database/migrations/default folder
Migration commands can take a context (name pending) that points to a folder inside directory
context defaults to default
An empty context doesn't add a folder
directory defaults to resources/database/migrations/
If there is a cfmigrations.json file in the migration directory & context, the values in the file should be read in, ENV vars expanded, and replace the default configuration from box.json
Commands like install and uninstall need to take a directory and context parameter so they can use the new cfmigrations.json config
cfmigrations connection info in box.json and cfmigrations.json need to take an additional top-level parameters of table, defaults to cfmigrations.
Should migrate init create a resources/database/migrations/default/cfmigrations.json file?
Add ability to set a default context for the module.
Backwards compatibility questions:
Do we even use box.json anymore?
Do we expect users to update old sites by either passing in context="" or moving into a default folder.
elpete
commented
1 year ago
New features:
resources/database/migrations/defaultfoldercontext(name pending) that points to a folder insidedirectorycontextdefaults todefaultcontextdoesn't add a folderdirectorydefaults toresources/database/migrations/cfmigrations.jsonfile in the migrationdirectory&context, the values in the file should be read in, ENV vars expanded, and replace the default configuration frombox.jsondirectoryandcontextparameter so they can use the newcfmigrations.jsonconfigbox.jsonandcfmigrations.jsonneed to take an additional top-level parameters oftable, defaults tocfmigrations.migrate initcreate aresources/database/migrations/default/cfmigrations.jsonfile?Backwards compatibility questions:
box.jsonanymore?context=""or moving into adefaultfolder.