You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think that it would be a good idea to host some DietPi images on IPFS, as an optional download option. I do already have a up-to-date mirror of the disk images directory at /ipns/k51qzi5uqu5dit856p8codd8mdkhfgic8m93jl4i2udrr1o35uvtnc2nbvtfyi.
The text was updated successfully, but these errors were encountered:
Quite an idea. But we'd need to find a way to do IPFS file updates directly from our server to avoid doubled upload but without doubling disk usage on our server, which is limited. Like a daemon that watches image file changes via inotify and in case feeds them into a local IPFS node or so, or can the node do such by itself? But the disk usage for that node needs to be limited, much lower than the actual images size, not sure if/how that would work, e.g. supporting it with other nodes from community members.
Some of the benefits of IPFS are btw not that huge in our case, due to do Cloudflare cache which has most of the frequently downloaded images decentralised available. I set 1 month TTL for those, clearing single images cache on demand, but as only ~50-60% of bandwidth is served from the edge cache, they are not really all served from cache (which I would expect with 1 month cache time).
I think that it would be a good idea to host some DietPi images on IPFS, as an optional download option. I do already have a up-to-date mirror of the disk images directory at /ipns/k51qzi5uqu5dit856p8codd8mdkhfgic8m93jl4i2udrr1o35uvtnc2nbvtfyi.
The text was updated successfully, but these errors were encountered: