Revamp to better flow

[chez14]

We'll move the migration status to database (and file), and adding new tracking for each migration. I think. This idea needs to be brainstormed so I'll post the updates in this issue.

[chez14]

Database schema:

• ilgar_migration
  • id, int, PK
  • version, text
  • executed_on, datetime

Usecase:

• Migration will check on latest version, eg. by sorting the version of the migration from the DB.
  • System will scan migration directories, then rule-out the one that has been migrated from the DB. We'll call this as resync migration. → Will be default behavior.
  • System will only migrate the one that are newer from the DB. The old one that are not yet migrated will be ignored. This will be the normal and default migration strategy. → Cancelled because this is not actually that normal and will not be implemented this time.
• Revert Migration. Migration will check from DB and check what's migrated and what's not.
  • If there's migration that are listed on DB, but not present on the file system, we'll ignore them by default and send some warning. On "strict revert" strategy, this will throw an error and stop it being continued.

[chez14]

Potential new settings param:

• migration_strategy, possible values normal, resync
• revert_stategy, possible values normal, strict
• migration_table_name, default to ilgar_migration migrations.
• database, default to DB.
• store, default to database, potential values database, file.

Potential shared info:

• get migration version
• get migration list

[chez14]

Questions:

• Do people need "soft" fail for migration?
  e.g: things doesn't run as expected, so we can just run return false. → I think this will be bad because the return thingy should give us what makes it error. → i think we can create an helper like $this->failIfFalse(....)

[chez14]

Next TODOs for Ilgar:

• Turn off the web access by default.
• Add default settings handler test
• Add revert functionality with extra parameters for "strict revert" or not. (Strict revert means it will stop running if the original migration script is not there).
• Add Extra API for
  • get migration version
  • get migration list
  • Revert via API