6 ms·
Yes! Well said. It would definitely need to include: * Web code editor for jobs (JS, Python, Ruby, Perl, Go, etc., etc.) * Results served over an authenticat
by sakai 12y ago
Yes! Well said.
It would definitely need to include:
* Web code editor for jobs (JS, Python, Ruby, Perl, Go, etc., etc.)
* Results served over an authenticated API (e.g., servicename.com/api/<username>/<jobname>/files/result.csv would get you the latest result.csv file generated by your script, .../<jobname>/20140419/files/result.csv would get you yesterday's, etc.)
* Jobs could probably be both scheduled (i.e., cron-like) or triggered via a webhook
- olegp 12y agoMight make sense to stick with JS to start with for the sake of simplicity. I actually wrote a Node.js PaaS that I never open sourced & periodic short lived jobs was one of my use-cases. Let's continue via email.
- notduncansmith 12y agoHey guys, too late to get in on this discussion? Sounds really cool and something I could see myself using a lot. hello at duncanmsmith.com