Eiso Kant
Eiso Kant
We're half way there. Right now @rporres is able to do this, and we use them (they are based on the current `Dockerfile` at the root of this repo). However...
Another alternative is having cached data for a (limited) set of queries, this way, we could 'mock' an engine environment.
To learn more about how @src-d/infrastructure does it today: https://github.com/src-d/infrastructure/tree/master/engine-jupyter-demo
From what I understand about Spark we'd need to also move away from Derby (https://github.com/src-d/engine/issues/192) to allow multiple Spark sessions and a we'd need heavy caching across all sessions.
@bzz because of @rporres's comment of how feasible it is to scale with individual instances (not containers) per user. @rporres since they are temp containers, could we do something like...
This will open up again once gitbase is ready, right now it's on pause till performance is where it needs to be.
Browser: `Google Chrome Version 65.0.3325.181 (Official Build) (64-bit)` Pulled latest docker container today: `v0.6.1`
It's very minor, if not easily fixed, absolutely fine to keep it like this.
I encourage someone to make a PR to the README of the guide, or create an engineering/README with a ToC.
@bzz I am assigning this to you, for now, feel free to reassign and choose the appropriate priority.