Blog post detailing quick install of IPFS latest #8
Conversation
| collection: posts | ||
| --- | ||
|
|
||
| The best way to provide content using [IPFS](https://ipfs.io) is to run your own IPFS node. You can do this by running an IPFS node on your personal computer, but that will only work as long as your computer is running. For hosting content with a higher availability, you need to run an IPFS node in a datacenter. That ensures your content is always online and available to other nodes on the network. |
There was a problem hiding this comment.
since so much of the pitch for ipfs is to not necessarily require the datacenter, would be good to say this is useful but not needed. basically, something more like:
The best way to provide content using IPFS is to run your own IPFS node. You can do this by running an IPFS node on your personal computer, but that will only work as long as your computer is running. For users running mostly from laptops or with bandwidth constraints, it is useful to run IPFS nodes in a datacenter, and pinning the content there too. This ensures your content is replicated, online, and available to other nodes on the network.
|
@kyledrake some feedback above o/ -- otherwise, this is great!! may be useful to have an "install on digital ocean" button: @lgierth did we ever experiment with these? i dont recall actually using it. |
|
We didnt, in fact. CCCamp just flew by, didn't even get to setting up the NUCs :) DigitalOcean have an install button of their own now, I think, but I can't find the link. |
|
I like the idea of a one-click install, but I don't like the idea of sending that through a third-party server. We would be using a third party server not using verification to install an unsigned non-release of IPFS. 💣 I'm actually already pretty uncomfortable not having a way to do signed releases right now. Going forward, IPNS keypair security for larger sites is going to have, in many respects, the same security concerns as Bitcoin keys and I think it's important to start thinking about it that way. The right approach here is to get some debian/ubuntu packages up-and-running for IPFS (with a signing key). Then the install process here becomes a single command: I would love to explore getting a debian package going. I'd prefer that to having 5+ different ways to install IPFS that are all... not ideal. Perhaps it makes sense to file an issue for this to discuss? I would be more than happy to work on this! |
|
@kyledrake changes look good! thanks! i didnt see them because github doesn't notify on pushes -- can you post again (or assign the issue) when you push after CR? I still think these are important:
Less important, but maybe? your thoughts? |
|
asciinema would be so nice |
|
Closing in favor of #73. |
No description provided.