Repeatr: Reproducible, hermetic Computation. Provision containers from Content-Addressable snapshots; run using familiar containers (e.g. runc); store outputs in Content-Addressable form too! JSON API; connect your own pipelines! (Or, use github.com/polydawn/stellar for pipelines!)
I'm starting to get time to look at actually slowly starting to play with repeatr. One thing that I don't 100% understand yet, is where data is stored/cached. When I scan something in, is it cached somewhere in var? What about when I run a formula? Docker, of course, stores everything in /var/ and the current recomendation for subuser that I give is to just nuke /var/ and run "subuser repair" to rebuild everything every couple of months. However, this isn't exactly elegant :P !!!
I recently watched a film about EU privacy regulations called Democracy . It was pretty interesting, so you might check it out. In the film, the guy that architected the privacy regulations came up with the following fundimental model: Before a company can store personal data, it must first get the consent of the user, and at the time the user gives consent, the company must describe what data is stored, what it is used for, and how long it is stored. And the company is forbidden from storing it for longer than necessary. I think that this general philosophy can also be applied to caching gigabytes of "stuff" in /var/. I want.
[ ] repeatr run -h # Should say what run stores, where, and for how long.
[ ] repeatr scan -h # Should say what scan stores, where, and for how long.
I'm starting to get time to look at actually slowly starting to play with repeatr. One thing that I don't 100% understand yet, is where data is stored/cached. When I scan something in, is it cached somewhere in var? What about when I run a formula? Docker, of course, stores everything in /var/ and the current recomendation for subuser that I give is to just nuke /var/ and run "subuser repair" to rebuild everything every couple of months. However, this isn't exactly elegant :P !!!
I recently watched a film about EU privacy regulations called Democracy . It was pretty interesting, so you might check it out. In the film, the guy that architected the privacy regulations came up with the following fundimental model: Before a company can store personal data, it must first get the consent of the user, and at the time the user gives consent, the company must describe what data is stored, what it is used for, and how long it is stored. And the company is forbidden from storing it for longer than necessary. I think that this general philosophy can also be applied to caching gigabytes of "stuff" in /var/. I want.