search

qri-io / rfcs

Request For Comments (RFCs) documenting changes to Qri
MIT License
12 stars 6 forks source link

RFC: cron #42

Closed b5 closed 5 years ago

b5 commented 5 years ago

oook, the more I think about this, the bigger it gets. I'd love feedback. @rgardaphe I've tagged you b/c I'm trying out a new "term of art": fog service. Aside from the usual technical vetting, I'd love to hear other's thoughts

b5 commented 5 years ago

While working on the proof-of-concept code after the qri update refactor, I've realized that this should also work as part of this RFC, given that we're aiming for parity between the arguments for qri save and qri update schedule:

qri update schedule --body path/to/file.csv me/dataset_name R/P1D

meaning we can schedule manual transforms as well as scripted transforms. This opens the door to UI that lets a user drag an excel file over the frontend and "schedule routine saves" that automatically creates new versions of a file. Combine this with dropbox-style directory syncing and we have a really nice collaboration & audit workflow.

The downside: if the filepath ever changes, scheduled updates will break. I think it's worth it, given that with this users can create "data feeds" from an excel file without writing a line of code.

b5 commented 5 years ago

Ok, changes made. re-requesting for final review