Prepare CI to build the new react frontend component

[lbroudoux]

In the context of #76, we need to build a new Hub container image that provides the next version. We must adapt the CI pipeline to also build this additional image.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[lbroudoux]

We still have an issue with:

8.440 src/services/package.services.ts(13,11): error TS6196: 'Package' is declared but never used.

when compiling the react part.

[pplancq]

Hello,

As I'm new to the project, I haven't fully grasped all the ins and outs yet. However, I can leverage my expertise in React to help optimize your migration to this framework.

I noticed that a Package type was defined but not used, which appears to be causing the error you encountered. If necessary, it is possible to temporarily bypass this issue.

Additionally, I would like to learn more about how your CI pipeline operates so that I can best assist in refining it.

[lbroudoux]

Hi @pplancq,

To give you a rapid overview of what we're trying to achieve, the existing https://hub.microcks.io is written in Angular 8, and the source code is in the /frontend folder.

We had a mentee during the May/June period who proposed refactoring it using React, and the WIP is located in the /react folder, waiting to be finalized. During this mentorship, we elaborated a - quite ambitious - plan that you can find here. The rough idea here was to modernize the frontend and backend before doing the changes to make the Hub deployable on-premises.

So basically the frontend refactoring/migration has just started and it is the first task to complete IMHO. The Package type you noticed there seems to actually be a partial translation of the APIPackage that was defined here in package.model.ts (and I'd prefer stick with the original name BTW 😉 ). We'd more than ever appreciate your help to finish this refactoring!!

Regarding the CI/CD process: it's actually super basic at the moment as it's just ensuring the typescript compilation is OK and then building a container image, launching a single Express server, embedding both backend and frontend. You can check the Dockerfile for the existing hub and the Dockerfile.next that takes care of the /react frontend.

Hope it helps./

[pplancq]

Hi, @lbroudoux
Thanks a lot for the details! If I understand correctly, the CI process should build the Dockerfile.next container, which includes both the server and the React frontend. I can take care of creating or improving the Dockerfile to handle that.
Just to clarify: the server included in this project is not just a development mock, right? It's the actual API server? Also, is the OpenAPI documentation up to date? It could be a great reference for the next steps on the React side.