I've merged a significant rewrite into the main branch and will be releasing it soon.
Before I do so, I want to let everyone know that this will be a major release which means some old functionality will be left behind and some new is coming and you should take care when upgrading.
Namely, backup the volumes you have bound for runtime cache and uploaded files. Those are bound to these container directories:
- /opt/runtime-cache
- /opt/uploaded-files
The database format has changed completely and is incompatible with the old version, after you upgrade to the (soon-to-be-released) version 2, you won't be able to come back to any previous version. For that reason, the only way to downgrade in case of migration failure is by using the aforementioned backup.
I've tested it a lot and the migration works well, but there's always the possibility that your instance has some weird edge case I didn't think of.
On the off chance you used the serverless deployment to AWS, it's now unsupported and Docker (or manual deploy) are the only supported options now. To migrate from Dynamo DB cache backend, I've added a app:migrate-dynamo command you can use.
The reason for this rewrite is simple, back when this project started, only very simple use-cases were supported and using a cache instead of DB was fine, but now I've basically implemented a few relational database features into a key-value cache storage and then I thought "Hey, you know what else has relational database features? Relational databases!" so here we go.
Pretty much nothing else has changed (except some general modernization and a few unrelated bug fixes), but this will make it possible to implement new features without losing my sanity.
It's been fixed, but as I said in the previous comment, you need to create the schedule again anyway.