ipfs-shipyard / ipfs-shipyard/scala-ipfs-api
Support for go-ipfs v0.5
- Dominant language
- Scala
- Stars
- 36
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
> This is a notice I'm filling in repo of every HTTP Client I can find.
> **Feel free to close it if this project already works fine with go-ipfs 0.5**
## POST-only HTTP API
go-ipfs 0.5 will block `GET` commands on the API port (https://github.com/ipfs/go-ipfs/pull/7097), requiring every command (RPC) to be sent as HTTP `POST` request.
See API reference docs: https://docs.ipfs.io/reference/api/http/
**This is potentially a breaking change**,
double check if this project uses `POST` for every RPC call.
## Testing
Download links for v0.5-rc* are available at https://github.com/ipfs/go-ipfs/issues/7109
You can also test using an ephemeral Docker container:
```console
$ docker run --rm -it --net=host ipfs/go-ipfs:v0.5.0-rc1
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Scala client entry points that send IPFS HTTP API commands and compare their request methods with the linked go-ipfs v0.5 API reference. Use the provided Docker command to run go-ipfs v0.5.0-rc1 and verify that every RPC works through POST requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100