Skip to content
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

ipfs cli command missing #1805

Closed
MysticRyuujin opened this issue Apr 19, 2021 · 3 comments
Closed

ipfs cli command missing #1805

MysticRyuujin opened this issue Apr 19, 2021 · 3 comments
Labels
need/triage Needs initial labeling and prioritization

Comments

@MysticRyuujin
Copy link

  • OS: Linux Mint 10
  • Version of IPFS Desktop: 0.14.0

Describe the bug
Disclaimer, first time trying to use any ipfs tools.

First I tried using the AppImage. After running the app I thought I would try to check out the cli, but ipfs command was not found. So, I tried to install the ipfs tool. First, I tried to install it via snap (yes I have snaps enabled on Linux Mint) but that resulted in it wanting to init a new repo. So I figured ok, I'll try to install ipfs-desktop through snap too. That...didn't work either. When I started ipfs-dekstop through snap it initialized its own repo....

Then I did more research and I found a few closed issues here about the ipfs cli tool being installed / placed in the PATH when installing, and they seemed to suggest that if I installed via deb package that I would get a working ipfs-desktop, and ipfs cli from that single install...That didn't seem to work either?

So here I am, trying to figure out how to get a working ipfs-desktop install AND a cli ipfs working together nicely.

To Reproduce
See above description 😄

Expected behavior
I install ipfs-desktop, I get ipfs cli tool..OR there are some clear instructions to make the two things work together...

Screenshots
N/A

Additional context
#727
#1039

@MysticRyuujin MysticRyuujin added the need/triage Needs initial labeling and prioritization label Apr 19, 2021
@welcome
Copy link

welcome bot commented Apr 19, 2021

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

@MysticRyuujin
Copy link
Author

I don't know in what order of operations I did to get this fixed, but I think that installing ipfs-desktop from the deb put the repo into ~/.ipfs and now manually installing the go-ipfs binary into /usr/local/bin has it working...but I don't know why installing the deb didn't include the ipfs binary...

@lidel
Copy link
Member

lidel commented May 4, 2021

We had experiment in the past when ipfs-desktop added ipfs to PATH, but it was too expensive to maintain: it did not work reliably, clashed with ipfs installed by some other package, and we ended up deprecating it (it is removed from UI right now).

In short, if you want ipfs in terminal, follow https://docs.ipfs.io/install/command-line/ or use go-ipfs daemon package for your OS.
ipfs will inspect $IPFS_PATH/api file and connect to it by default, so just make sure IPFS_PATH points at the same repo as one used by ipfs-desktop. You can also override the API addres via ipfs --api if you choose to have multiple repos.

I'm closing this, If you feel https://docs.ipfs.io/install/command-line/ was hard to find, let us know how we could improve it 🙏

@lidel lidel closed this as completed May 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

2 participants