web3.storage VS piku

https://web3.storage/ https://estuary.tech/

I'm building Flash — a service to deploy websites and apps on the new decentralized stack. It relies on public infrastructure (such as Estuary, web3.storage and others) instead of providing its own, making the bandwidth and storage very cheap and accessible.

https://web3.storage/ does everything you need

Web3.Storage and other similar projects run a network of IPFS nodes that allow users to store whatever content they like, as a kind of competitor to Dropbox or Google Drive: this could be their personal content, or again, any application content, because some apps integrate directly with this service via their API

You can file this as an issue in the repo here and perhaps mention to them that, as a user, it feels phishy to you.

Typically app developers would be the ones to build on Filecoin and you would choose an app like web3.storage to store your data. As a consumer you dont have to directly hold FIL but you benefit from the Filecoin ecosystem.

Filecoin may not have a front-end but our team has worked on https://estuary.tech and it has been easy for our users that have an invite to onboard to the Filecoin Network, another great option is https://web3.storage

clone repos to your computer, dont just fork them

the fork disappears when the parent repository is taken down, clones stay on your machine

upload to IPFS. you can pin on IPFS for free with filecoin. Use filecoin nodes to pin on ipfs at https://web3.storage

As for storing data on Filecoin directly, that would require making a deal with a Filecoin Storage Provider; doing so is currently a complex task but reading the documentation should get you somewhere. You will need a small amount of the FIL token to make the deal with an SP, who will then store your data. Keep in mind that something like web3.storage or Estuary.tech may be better for your needs if you need easy access to the files later; Filecoin can (currently) be thought of as closer to archival storage, but efforts are being made to make it more generally useful too.

I should add one to https://piku.github.io (spoiler - this doesn't use Docker at all)

I like it. I wrote Piku (https://github.com/piku/piku) with much the same interest in fixing some of my pains, so I get where you're coming from with this. Will drop it into one of my current projects to build ESP32 binaries :)

I never had any serious issue with SD cards since the Pi 2B (and I've kept Pis running for years).

Anyway, for those wanting to deploy more generic apps, that is why I initially wrote https://github.com/piku/piku - you still have to flash the OS (and rpi-imager does that with sane defaults these days), but once you're done you have Heroku-like deployments for any language runtime you install on the Pi.

I also have https://github.com/rcarmo/ground-init, a cloud-init like shim that simplifies setting up machines (I'm a big fan of cloud-init, but since Raspbian doesn't support it and Ubuntu on ARM requires some fiddling to make it work I decided it wasn't too hard to roll my own).

(I probably should look into glueing that into rpi-imager, but there is are only so many hours in the day...)

I automated that away a long time ago: https://github.com/piku/piku/blob/master/piku.py#L814

Piku https://github.com/piku/piku

So, stupid question: why couldn't I just use the 'baremetal' OS provided by Hetzner, install Postgres, Redis & node, create a separate db for each app, and run each app with https://github.com/piku/piku on a different port? For backups, I'll setup crontab to dump dbs locally and to S3.

piku?