stojanov-igor
commented
1 year ago Here are some additional requirements for the task above.
- [ ] Store the actual CID of the document in blockchain storage rather than showing it in the alert.
- [ ] Once the file is stored in IPFS, we should be able to fetch it and download it on the tasks page. You can check how to fetch/download the files at their API. See schreenshot.
- [ ] Implement unit tests for your functionality
- [ ] Make the connection to IPFS nodes configurable, instead of hardcoded. For example, we should be able to fetch files from the IPFS instance we have running at AWS: 52.91.119.196:8080
52.91.119.196:8080/ipfs/QmcDge1SrsTBU8b9PBGTGYguNRnm84Kvg8axfGURxqZpR1
Strech Goal
- [ ] Implement multi-file upload instad of single file. We should also be able to fetch all attachements relevant to the task.
Budget: 100 Euros
The front-end application is avalaible in the following repository: https://github.com/UniversalDot/front-end
Clone the repo and check out the branch that I have created for you.
Make sure that you commit everything to the existing branch. Once the task is completed, we will create a pull request to merge to
develop.Create a file uploader that allows the user to upload a file into the web application. The file uploader should use existing UI elements and styles. In more detail, the task should fulfill the following conditions:
Implement this file uploader for the
Attachmentinput insrc/pages/OrganizationOwn.tsxKeep in mind that the application is already connected to IPFS node running at http://109.235.70.27:5001. To see how the integration was done, check out the following pull-request: https://github.com/UniversalDot/front-end/pull/37
An example of a file uploader can be found here: https://www.npmjs.com/package/react-ipfs-uploader