ipfsclient
IPFS RPC Client
Installation
pip install ipfsclient
Documentation
https://ipfsclient.readthedocs.io/
Build docs locally
mkdocs serve
Tests
To only run tests: pytest
To run all checks: nox
Before running tests:
Regenerate pb2.py files
cd protobuf;
protoc --python_out=../proto --proto_path=protobuf protobuf/sample.proto
Ipfs setup
https://docs.ipfs.tech/install/
Run the ipfs daemon
ipfs daemon --api /ip4/0.0.0.0/tcp/5001
Check the status of your node at:
- http://localhost:5001/webui
- https://webui.ipfs.io/#/status
IPFS troubleshooting
Set the log level, send the logs to a file, and search the file for relevant messages
export IPFS_LOGGING=<debug|info|error>
ipfs daemon --debug 2>&1 | tee ipfs.log
cat ipfs.log | grep test_directory
If you find something important, you can show the first few lines around that message
grep -C 10 '2023-04-13T17:31:49.712-0400' ipfs.log
Here is an example of an error message in these logs:
2023-04-13T17:31:49.712-0400 DEBUG cmds/http http/handler.go:90 incoming API request: /files/mkdir?arg=test_directory
2023-04-13T17:31:49.712-0400 DEBUG cmds go-ipfs-cmds@v0.8.2/command.go:161 error occured in call, closing with error: paths must start with a leading slash
Metadata
Release files for ipfsclient 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ipfsclient-0.1.1.tar.gz | 5.5 kB | Without provenance | Details for ipfsclient-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ipfsclient-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for ipfsclient-0.1.1-py3-none-any.whl |
Total release size: 11.2 kB
Release files / ipfsclient-0.1.1.tar.gz
| Download URL | ipfsclient-0.1.1.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d49729f2438572b8d422cfbd3b7391e9887d01ade516cd5bbbbcbb19e8f52311
|
|
BLAKE2b-256 checksum How to use checksums |
21487f2c19af3dc95fde12276cd7a0cdaa469e214c381b174353dace1d92a94e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Release files / ipfsclient-0.1.1-py3-none-any.whl
| Download URL | ipfsclient-0.1.1-py3-none-any.whl |
|---|---|
| Size | 5.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f1c42ecc1400f305ac7fd69eca2eddf47eade0e871505728f9e42bb652a7982f
|
|
BLAKE2b-256 checksum How to use checksums |
5c9c96b3ddcc74daf9f2e352993409f6daa070ac0052f2c995ea0d2aeb166483
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Security for ipfsclient 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.