>
> The binaries are distributed using dtuf (
>> https://github.com/davedoesdev/dtuf
>> ),
>> which in turn uses The Update Framework (TUF) and a Docker registry to do
>> the
>> heavy lifting. You don't need the Docker client installed on your
>> computer.
>>
>
> For the less educated here, can you expand on what that means? Does that
> mean it uses some Docker tools without using the Docker infrastructure?
> (or am I grasping at the completely wrong straws?)
>
No, you've got it right. Docker make a server (the registry) and client
tools (the cli and daemon). I'm just using the registry here.
Version 2 of the registry is a generic content distribution server so you
can use it for anything, not just container images. Docker themselves run a
registry (the Docker Hub), which is what all the Docker clients get their
container images from. But you can also run your own registry on your own
server, which is what I'm going here. The reason I'm running my own is it
wasn't clear to me whether using the Docker Hub to store stuff than
container images breaks it's T&Cs.
> How does it handle updates?
>
When you run 'dtuf pull-metadata', it prints a list of files whic have been
updated since you last downloaded them.
>
> Any comments/opinions/feedback gratefully received!
>>
>
> Can you document the steps in the package README? (or the wiki, though
> follow the other thread to know when packages-wiki is in action ... any day
> now).
Yes, good idea.
>
>
> # Run it
>> qemu-system-x86_64 -enable-kvm -m 160 -kernel node -append '{"cmdline":
>> "node"}'
>>
>
> So I guess you can't really configure the guest in the current state of
> things, e.g. give it a network interface, at least not without using
> "rumprun -D" and some other kludges.
>
> I used the same approach of skip-rumprun-and-just-use-qemu for
> rumprun-nethack, and I liked it. However, I had the advantage of nethack
> always being nethack, so you don't need a flexible configuration.
Now we just need a flexible way to pass configuration :-)
Another thing I thought might be useful is the ability to bundle in a ram
disk image when baking so you can create a self-contained app image. For
Node it doesn't matter because you can bundle the app into the Node binary
itself but it would be handy for other things.
> I at least assume that you can do things beyond helloworld with node ;)
>
Yes, supplying an ISO with an example on is something I should add.
