Would like to support a dogg3rz configuration where the user can configure integration with IPFS either as an http (ipfs rest api) client or use IPFS embedded into dogg3rz binary.
There is currently a use case where some dogg3rz unit tests are dependent on ipfs and potentially CIDs that are produced. It would preferable to construct a unit test where an embedded ipfs client could be initialized during dogg3rz init node when standingup a unit test.
Also, there may be cases where a baked in ipfs instance is required in the same binary instead of an external ipfs instance or instances.
Would like to support a dogg3rz configuration where the user can configure integration with IPFS either as an http (ipfs rest api) client or use IPFS embedded into dogg3rz binary.
There is currently a use case where some dogg3rz unit tests are dependent on ipfs and potentially CIDs that are produced. It would preferable to construct a unit test where an embedded ipfs client could be initialized during
dogg3rz init node
when standingup a unit test.Also, there may be cases where a baked in ipfs instance is required in the same binary instead of an external ipfs instance or instances.