-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recommend installing IPFS Desktop rather than Go-IPFS directly. #253
Comments
This should probably be prioritized over some of the other hotfixes, since it's a big, meaty change that makes life easier for folks. I'm afraid I can't write this at present ... is there anyone else who would be wiling to take this on? It'd fall in two steps, really:
|
This will be dealt with in ipfs-inactive/docs#205. However we should keep this open until we've redirected all IPFS install paths down this route. From memory we'd need to update the following areas, please drop any others onto this issue so we can capture them.
|
@lidel pointed out the excellence that is the Tor download page: https://www.torproject.org/download/ |
Note that ipfs-inactive/website#348 addresses this on the front page of ipfs.io. |
Let's not forget to …
|
Sorry for digging up an old issue team. What I'm getting from reading the comments here is that we need to:
I'm gonna create new issues for the last two points, and this issue can serve to just recommend installing IPFS Desktop for new users. |
The Install section now clearly splits up each installation option, with IPFS Desktop right at the top. The only remaining task in this issue is to create an installation section for IPFS cluster / server set ups, which is duplicated in #355. Closing this issue. |
IPFS Desktop now installs the
ipfs
command line tool, and has an auto-update mechanism, and has installers for alot of the platforms: https://github.com/ipfs-shipyard/ipfs-desktop#installWe should encourage folks to install desktop as the default, and then have an "setting up a server?" link... which encourages folk to install ipfs-cluster rather than go-ipfs, as we have ansible and docker scripts for cluster, and it is optimised for running on a server out of the box, and a cluster of 1 puts you in a good position for scaling your things later.
See issue ipfs-inactive/docs#110 for another potentially good install instruction explainer: how much disk space do different instantiations of IPFS take?
Additionally, let's discuss whether/how to include pointers for "non-official" ways of installing IPFS. This arises from a few stagnant (and, as a result of this issue, closed) PRs in the website repo, including:
brew install
for Mac folkssnap
for Linux folksThe text was updated successfully, but these errors were encountered: