In previous versions, the p2wdb-pinning-service was an external application that ran in parallel to the P2WDB. It would be triggered by a webhook and would pin any content with an app ID of p2wdb-pin-001 by sending a pinning command to the external Kubo (go-ipfs) IPFS node.
With v5 of P2WDB integrating a Helia IPFS node into the app, there is no external IPFS node. It is now more appropriate to integrate the pinning feature right into P2WDB. That's what this release does.
Pinning is turned off by default. To enable the pinning feature, set an ENABLE_PINNING environment variable to any value. When new DB entries with an app ID of ipfs-pin-001 are validated, the content the entry points to will also be downloaded and pinned by the Helia IPFS node integrated into the P2WDB.
In previous versions, the p2wdb-pinning-service was an external application that ran in parallel to the P2WDB. It would be triggered by a webhook and would pin any content with an app ID of
p2wdb-pin-001
by sending a pinning command to the external Kubo (go-ipfs) IPFS node.With v5 of P2WDB integrating a Helia IPFS node into the app, there is no external IPFS node. It is now more appropriate to integrate the pinning feature right into P2WDB. That's what this release does.
Pinning is turned off by default. To enable the pinning feature, set an
ENABLE_PINNING
environment variable to any value. When new DB entries with an app ID ofipfs-pin-001
are validated, the content the entry points to will also be downloaded and pinned by the Helia IPFS node integrated into the P2WDB.