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.

Sign up for GitHub

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

Jump to bottom

How to use Boxo library or SDK for IPFS with Go language? #451

Closed
unicornlox opened this issue Aug 23, 2023 · 5 comments
Closed

How to use Boxo library or SDK for IPFS with Go language? #451

unicornlox opened this issue Aug 23, 2023 · 5 comments
Assignees
@hacdias
Labels
need/author-input Needs input from the original author need/triage Needs initial labeling and prioritization

Comments

@unicornlox
Copy link

unicornlox commented Aug 23, 2023 •
edited by Jorropo

Hello,

I could not find any documentation on how to use ipfs boxo. In short, I want to use ipfs with the go language, and when I look at the information about kubo, there are old libraries. Where are the current documents on how to use ipfs with go? If anyone has information, please help.

Thank you for your support.
@unicornlox unicornlox added the need/triage Needs initial labeling and prioritization label Aug 23, 2023
@welcome

This comment was marked as resolved.

Sign in to view
@lidel
Copy link
Member

lidel commented Sep 18, 2023

@unicornlox does ipfs/kubo#10096 (comment) answered your question, or do you feel we should add more examples in Boxo?

@lidel lidel added the need/author-input Needs input from the original author label Sep 18, 2023
@BigLep
Copy link
Contributor

BigLep commented Oct 5, 2023

2023-10-05 maintainer conversation: this should be closed because lacking author input. @hacdias is going to get the bot going for this repo.

@hacdias
Copy link
Member

hacdias commented Oct 9, 2023

@BigLep I checked some other PRs and they've been hit by the bot, I'm not sure why this one hasn't. cc @ipfs/ipdx

@hacdias hacdias closed this as completed Oct 9, 2023
@galargh
Copy link
Contributor

galargh commented Oct 11, 2023

@hacdias That's because it still had need/triage badge on. That label prevents the automation from automatically closing an issue.

@BigLep BigLep mentioned this issue Nov 9, 2023
Closed
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hacdias hacdias

Labels
need/author-input Needs input from the original author need/triage Needs initial labeling and prioritization
Projects
No open projects
IPFS Shipyard Team
Archived in project
Milestone
No milestone
Development

No branches or pull requests
5 participants
@BigLep @lidel @hacdias @galargh @unicornlox