-
Notifications
You must be signed in to change notification settings - Fork 465
Closed
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps updif/easySomeone with a little familiarity can pick upSomeone with a little familiarity can pick upeffort/hoursEstimated to take one or several hoursEstimated to take one or several hourskind/maintenanceWork required to avoid breaking changes or harm to project's status quoWork required to avoid breaking changes or harm to project's status quostatus/readyReady to be workedReady to be workedtopic/docsDocumentationDocumentation
Description
There are two Install guides on docs.ipfs.io: https://docs.ipfs.io/install/command-line-quick-start/ and https://docs.ipfs.io/how-to/command-line-quick-start/. They are slightly different, for example, the latter one instructs Mac users to download the x86 version, which is not supported by current OSX versions any more.
When installing IPFS that way, users will run into problems with OSX Gatekeeper, since the binary is not properly signed. Maybe we should recommend using Homebrew to install IPFS? Otherwise, we might want to add some text how to add an exception for the Gatekeeper.
Metadata
Metadata
Assignees
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps updif/easySomeone with a little familiarity can pick upSomeone with a little familiarity can pick upeffort/hoursEstimated to take one or several hoursEstimated to take one or several hourskind/maintenanceWork required to avoid breaking changes or harm to project's status quoWork required to avoid breaking changes or harm to project's status quostatus/readyReady to be workedReady to be workedtopic/docsDocumentationDocumentation