> > Seems to work. It feels like a very complicated way to use ftp, at least > for a one-off installation ;) >
:-) dtuf uses The Update Framework (https://theupdateframework.github.io/). It's basically a spec and library (in Python) for software update systems. It maintains metadata which identifies whether updates exist and downloads files that are required for the update. It also performs integrity and authenticity checks on the downloaded files. I could have used an ftp server for a backend (still could) but it's not as cool sounding then ;-) If you don't care about tooling or the checks TUF does then just sticking the binaries on Github Releases would be another way. A couple of other side points: - Docker themselves use The Update Framework in their tools. They had to port it to Go because they're a Go shop. Also, they have a separate server for storing all the TUF metadata called Notary. It does the job of doing all the crypto stuff so that instead of doing distributed 'web of trust' (passing public keys around), everything's done the under the auspices of your Docker account. - Just to be clear, the Docker tools aren't needed here on the client and just the hypervisor is used to run the Node binary. This is off-topic but what I want to do is then orchestrate the hypervisors using a tool like Saltstack. > So can you run anything beyond helloworld now, and what is the envisioned > path to making it possible to run some other node programs? > Pass in an ISO with the program on it and then point the cmdline to the program. I'll do that next before adding to README/wiki.
