One thing I really like and appreciate is that there's a dockerfile right in the root of the project, which makes spinning up a container a relatively nice experience... haven't run it or looked into the code though... that just struck out at me...
Looking at the dockerfile, it seems pretty big, and it also strikes me slightly that they have dependencies on node, ruby and go, along with mysql and redis. The UI appears to be react based.. not sure what's running in ruby.
I think it's nice that they support Docker, but I was disappointed that their entire installation instructions were "install docker then run our image". I had to read the dockerfile and the "start" script to find out what the actual dependencies and setup steps are.
I agree that a dockerfile isn't perfect, but it's not that bad either as a machine readable install guide that doesn't fall out of date as easily as documentation written for human consumption.
I definitely appreciate projects having Dockerfiles included, but yeah, that's not a good one. They should simply include instructions about how to link it to MySQL/Redis, or use something like docker-compose.
The way it's done now makes it inherently unscalable. Also, there are so many steps that it makes pushing an image to a Docker repository a massive pain.
Slightly weird that they didn't use node's module for that (which uses the compiled sass), since the front end is a react application, and seems to use node for building.
Looking at the dockerfile, it seems pretty big, and it also strikes me slightly that they have dependencies on node, ruby and go, along with mysql and redis. The UI appears to be react based.. not sure what's running in ruby.