10 commits

Author	SHA1	Message	Date
fr33domlover	7c2faa7faa	Email tokens expire within 1 day	2018-04-01 03:02:35 +00:00
fr33domlover	c5a50c336e	Adapt to persistent-migration changes ... We have gained: * Haskell-side validation of schema changes before their execution * Report of results of migration process * Handling of old deployments However: * The validation code hasn't been tested yet at all * Most of the migration list hasn't been applied at all yet * Adding lists of entities from a model file is NOT VALIDATED!!! It's totally possible to implement, just need to catch all the small details right	2018-03-31 19:22:37 +00:00
fr33domlover	bec9290783	Complete DB migration list, allowing to upgrade 2016-08-04 running instance ... Until now the list of DB migration actions was incomplete, containing only changes made since I added the migration system itself. It now contains the 2016-08-04 model, and then every change made since then. IMPORTANT: The 2016-08-04 instance doesn't have a schema version entity at all, so it is assigned version 0, while the actual version of its schema is 1. I'm going to patch persistent-migration to allow it to be 1, making the migration path smooth.	2018-03-27 14:28:56 +00:00
fr33domlover	3398b56931	Switch to yesod-auth-account and make the mail code independent of Vervis	2018-03-03 21:33:59 +00:00
fr33domlover	fb47407f2b	Adapt to changes in persistent-migration	2018-02-27 03:03:24 +00:00
fr33domlover	3b4bd2a5e8	I made upgrades to the DB migration system in Funbot, apply them here too	2018-02-25 11:14:07 +00:00
fr33domlover	fc556e0eb3	Workflow scope field, minimal support	2016-09-01 17:40:02 +00:00
fr33domlover	6b4ecb99c7	Migration: Repsert, not update, otherwise schema version never saved	2016-09-01 17:38:44 +00:00
fr33domlover	7218262223	Don't update DB schema version if equal to app's version	2016-08-31 17:12:20 +00:00
fr33domlover	dc74456a6a	Use the new migration system in place of persistent's one	2016-08-31 16:51:02 +00:00