Show HN: Domino, a PaaS for data science
dominodatalab.com
dominodatalab.com
This means that your data (in files) needs to be in the working directory, and is versioned along side your code. Sounds pretty cool, but I am not sure how it would scale for large / constantly changing data sets.
If your code pulls data from a database (e.g., kelv's test cases), one option is to save the DB snapshot out to a file when the code runs. After we finish executing your code, we snapshot all the new/changed files in your working directory (we call those the "results" of the run). Using this approach, you'd have a record of the DB snapshot for each run of your tests. But, again... if your snapshot is more than 10s of GB, the network transfer time could get annoying.
[0] We treat the working directory as a git repo, but since git breaks down with large files, we only use it to track your directory structure; we store actual file contents elsewhere.
Second, it centralizes the storage of project data, enabling.
And the next sentence should be And third, not And second: And second, Domino automaticallyWe allude to this in our FAQ ("What if I want to run C++ code...") but we'll update the docs to make the specific instructions more clear.
much love!