Microfront Hosting App
This is the orchestrator app for microfronts, and it's responsible for two main things:
- Loading Microfronts
- Displaying Microfronts
Internal Open Source
Owners
Curators
TBA
Contribution guidelines
- Sync with this repo's owners.
- Make sure every contribution has appropriate test (unit and component) coverage.
- Remember to reflect your changes, if required, in the Readme file.
- Participation in this repository is subject to Freightos code of conduct.
- Make sure to read and follow the FE Guild PR Guidelines
How to set up
Information on how to run and operate is Running Microfronts locally Run cloud Microfronts on local environments Run local Microfronts on cloud environments
Release procedure
More information about Microfronts current pipeline Pipeline for Microfronts All the steps of the pipelines flow can be followed through the slack channels: 1- mp-ci: Notifies about all the stage processes of the CI pipeline 2- mp-cd: Notifies about all the stage processes of the CD pipeline 3- mp-cd-build: Notifies that a feature / bug fix is released to production
Kill switches
Features susceptible of malfunctioning should be wrapped with an appropriate kill switch.
SonarQube
No specific SonarQube analysis exist for this repository.
Slack channels
No specific Slack channels exist for this repository.
Creating and connecting microfronts
Check Microfronts Skeleton to build your own
How it works, Internally?
- First step is to load microservices config files (Contains endpoints and plain routes)
- When loading the application there is wildcacrd route
ComponentsFactory -
ComponentsFactorystarts doing route matching, read from the config - When there is a match first we load the local file for the Microfront
- Then we load the real routes - with loadables components - and load the right page