Add "create dat archive" and "import content from GitHub if Travis tests pass"

[rjcorwin]

I'm officially working on a team building an app that will likely use Dat as it's primary means of distribution. We need multiple developers to be able to deploy to our production Dat URL that I'm assuming will stay the same throughout the apps life (unless that turns out to be a security issue). It would be great if a central authority like hashbase could hang onto the private key for the archive and give us UI to decide where to import content from. From where? Probably a GitHub repo given that's how we collaborate on code, bonus points for only deploying when Travis tests pass. The mechanism is similar in concept to how docker hub allows us to automatically build given an update to a GitHub repo.

This may not be THE answer, but I figured I'd throw it out there. An MVP for this feature might be to import content from another dat so when we r ready to deploy, our build machine does it's build and then dat share. We then take that new dat url and paste it into hashbase to copy over the content into the app's canonical dat.

[pfrazee]

I've been thinking about setting up a "hosted dat" mechanism which you can RPC to. That'd be a very generic way to accomplish what you want to do. We could probably add UIs for adding and removing files on those, too.

The "import content from GitHub if tests pass" usecase is pretty niche for us right now. I'm not sure that'd be a good place for us to put resources, but you should be able to build a tool that does something similar if you can RPC to a dat on hashbase and do reads & writes.