While RCO uses a SQLite database in normal usage, early on we started with an in-memory database - so all logic was in JS.
We haven't used the mock backend for a few months, and it is now out of sync with the normal database - especially with the Soul-Auth changes.
We're going to comment out the mock database. Should there be a large development project in the future, there may be merit in re-instating the mock backend, but a cost-benefit decision will have to be made regarding that.
Change let's switch to Heroku publishing an instance of RCO/VAL running the Soul/SQLite backend. Database changes will be lost each time Heroku goes to sleep, but it will allow a proper review of new features.
While RCO uses a SQLite database in normal usage, early on we started with an in-memory database - so all logic was in JS.
We haven't used the mock backend for a few months, and it is now out of sync with the normal database - especially with the Soul-Auth changes.
We're going to comment out the mock database. Should there be a large development project in the future, there may be merit in re-instating the mock backend, but a cost-benefit decision will have to be made regarding that.
Change let's switch to
Herokupublishing an instance of RCO/VAL running theSoul/SQLitebackend. Database changes will be lost each time Heroku goes to sleep, but it will allow a proper review of new features.