Currently, the IPFS JS library that we have, creates a node on the spot. Then files added to that node are only accessible while the web session is opened (it depends on local storage of the browser). This is is not ok given that data needs to be stored in the cloud, not locally.
We should use a client and not a node.
I set up an IPFS node in my server meanwhile (we could set up one in DEF servers once they are ready-to-go), and will include an IPFS api JS library to connect to that node remotely. Data will be stored there and replicated to IPFS standards.
Currently, the IPFS JS library that we have, creates a node on the spot. Then files added to that node are only accessible while the web session is opened (it depends on local storage of the browser). This is is not ok given that data needs to be stored in the cloud, not locally.
We should use a client and not a node.
I set up an IPFS node in my server meanwhile (we could set up one in DEF servers once they are ready-to-go), and will include an IPFS api JS library to connect to that node remotely. Data will be stored there and replicated to IPFS standards.