Hi there! We got familiar with the mediterraneus protocol and its components through some testing and documentation provided by LINKS. The marketplace frontend currently features a wizard to onboard new participants, but it is not hooked to any of the components, since their scope are still being defined. The goal of this issue is to integrate the components to make this onboarding process fully functional.
So to consider this issue closed, we need to:
[ ] have configurable docker images for each Mediterraneus components needed during the onboarding process.
[ ] have a docker compose and/or some instructions to bring up the mediterraneus components for testing
[ ] update the env variables of the frontend to point towards the mediterraneus components
[ ] remove example resources in the onboarding wizard and make it work with the components
[ ] update the README to indicate how to run the docker compose, and where to find the resources to perform the testing of functionalities like the onboarding (how to get dummy tokens from a given faucet, ...)
NB: At the date of writing, the onboarding wizard (accessible upon clicking the register button) is the only functionality depending directly on the mediterraneus components. Other DLT interactions will be performed indirectly by other components (DS connector, and maybe also catalogue).
Hi there! We got familiar with the mediterraneus protocol and its components through some testing and documentation provided by LINKS. The marketplace frontend currently features a wizard to onboard new participants, but it is not hooked to any of the components, since their scope are still being defined. The goal of this issue is to integrate the components to make this onboarding process fully functional.
So to consider this issue closed, we need to:
This issue should be address before the scopes of the Mediterraneus components are fully defined, i.e. until the following issue https://github.com/Sedimark/dlt-connector-rs/issues/6 is addressed.
NB: At the date of writing, the onboarding wizard (accessible upon clicking the
registerbutton) is the only functionality depending directly on the mediterraneus components. Other DLT interactions will be performed indirectly by other components (DS connector, and maybe also catalogue).