Updating for hyper:// and an easy install for users

[zootella]

From a discussion in Discord, here are a few ideas that (may) come together:

• The "closed laptop" problem. I wrote a Beaker+Agregore app; I want to make sure that it loads for anyone who navigates to it; so I can't turn off my computer anymore. :(
• Neither centralized, nor PC-to-PC, rather: Federated. Desktop and laptop PCs are waning as a consumer platform (in place of smartphones and tablets and streaming TV sticks). Saying your thing is for everyone in the world, but then not having a way to access it from even mobile web, is increasingly problematic.

Here's what were thinking to make:

• Easy instructions that non server admins can follow to rent a low cost ($5/month) VPS, and type a few commands on the command line, then...
• navigate a regular browser to your VPS's IP address, where a HTML UI lets you (and only you, the administrator) sign in, where you can...
• paste in your hyperdrive address, and have your server join the swarm. Now you can turn your computer off 💻😴

Features we can build on this later:

• More ability to see and limit how much bandwidth your server is using (because really, you just want it there for availability--once a swarm gets going, it's better if everyone just peers bandwidth)
• Actual HTTP/HTTPs delivery of content from the hyperdrive

From this launchpoint, lots of weird/cool stuff we haven't even thought of yet may be possible. For instance, a blog site where you can get started on either a hyper-enabled browser or a traditional one (that has, in its back-end, one of these federated hyper servers), move your blog back and forth or have it be both places, have super huge files only available on hyper (and thus, turn individual blog content into an on-ramp for new users to the decentralized web)

@RangerMauve @pfrazee

[zootella]

Inspired in part by this cool thing Secure Scuttlebutt has: https://github.com/ahdinosaur/ssb-pub#one-click-setup

[RangerMauve]

A one click setup for dat-store would be awesome.

Here's some of the things that might be good to look into:

• Setting up a docker image for Node and running dat-store inside it
• Exposing both it's HTTP port and it's hyperswarm TCP/UDP port
• See if this works

Then we'll want to make it easier to use

• Add a basic web UI to the index, could serve some static assets in the server.js using whatever Fastify plugin exists for static files
• Check out the server.js file for the endpoints and what they do
• Make them available in the UI (add, remove, list, proxy)

Then if that works we'll want to add security

• Mixing LetsEcnrypt (maybe with NGinx) into the docker script for automatic HTTPS (will need a domain for this? Is there an existing thing we can copy?)
• Add HTTP basic auth to the root page or whatever admin UI we make which can be configured on setup. (Probably easiest for access control restrictions, less to invent, easier to pass the URL around)

At any point in here a one click install on Digital Ocean could be useful, IMO.

Any questions about the steps? I can help guide to resources for how to do the individual steps, but I don't have the bandwidth to implement all this in my spare time at the moment. :P Might be down for doing a short term contract if folks are interested in funding work on it though.