oduwsdl
Decouple IPWB from IPFS
Currently, IPWB stores configs in the IPFS config file rather that its own config file (#234). This is particularly problematic when trying to Dockerize it or running IPFS on a different host. In order to store certain IPWB configs, IPWB tries to locate the IPFS config file, which may not be locally available on the same host/container.
This ticket is to track not just the config file coupling, but any other changes that are required to make the two components run independently. In order for IPWB to work, it should only check whether an IPFS endpoint (as configured via configs/env vars) is responding.
@ibnesayeed I believe we ought to outline the dynamics and some use cases of using a remote IPFS daemon from ipwb.
If it has to work beyond a toy example of small sample WARCs on any serious scale with persistence, a separate IPFS server is almost going to be necessary to have. This current one to one coupling (one instance of IPFS running on the same host with one instance of IPWB) is not practical beyond testing and playing with the system. The system should work in a way that many IPWB instances can be connected to a single IPFS server or multiple IPFS servers exchanging data with each other, of which some might be serving their own IPWB instances.
Related effort/feature suggestion: https://github.com/ipfs-shipyard/ipfs-desktop/issues/602