fallenhitokiri
commented
8 years ago What you describe sounds a lot like the in-memory datastore with persistence I was thinking about - at least as one of the options.
Not related to the datastore I'll add an export / import function to the todo list. This will likely fit in nicely when I continue to work on the "worker" implementation to run builds on different system than the one "leeroy leader" is running on.
Allow exporting and importing the database via web. Consider doing it with
bson, or even just plain-text json. As I see you're considering moving away from SQLite, perhaps consider storing the data in a schema-defined JSON. The dataset should always fit to memory, logs can be stored on filesystem as access to them is usually O(1) - one project at a time