Agis Anastasopoulos

Right now, we implicitly require administrators to have Redis configured with `maxmemory` and `maxmemory-policy` set to `allkeys-lru`. While this is convenient for us, it's not very bullet-proof since we don't...

Currently, we default it to a very big number (999999) to effectively disable it (because no jobs take more than that). That doesn't make much sense, we should instead be...

Currently we use plain `puts` inside `Worker` and `Reporter` to print various rspecq-level events like errors or warnings. However this mixes the output from that generated by RSpec and makes...

Currently we keep a single timings key (`timings`). If that is somehow lost, all scheduling is then thrown out of the window. To avoid mishaps, we could also store the...

This seems like a more sensible default. However this is a breaking change.

Currently, if `data_path` is a symlink, docker on Mac complains with: ```shell $ ./mistry-cli build --host localhost --project simple 2018/04/12 13:21:47 Error creating job: Error building {project=simple params=map[] group= id=3dc923b}:...

We currently load React from the web. We should embed it in the binary.

Users should be able to expand/collapse irrelevant or long log output sections (eg. `bundle install`) from the log output, so that they can focus on the stuff that matters.

In the index page (job list), one should be able to sort by project, build time, status etc.