...
Each repository above contains a helpful README file.
Front End How To - but specifically: Micro Frontends How To
MFE Definition of Done to see what it takes an MFE from “Planning” to “Done”.
MFE Rewrite Status to see the status of our many frontend features.
Open edX Developer Docs: https://edx.readthedocs.io/projects/edx-developer-docs/en/latest/developers_guide/micro_frontends_in_open_edx.html
Architectural decision records (ADRs) are in the
docs/decisionsdirectory of each frontend-app-* repo.
...
The frontend-platform repo contains code to take process environment values and place them in an MFE-accessible config. For process environment variables to become part of the MFE config, they need to be added to the TODOcode here.
MFE Addition
TODOTo use the new MFE config value in development, the value must be added to the .env* files in the MFE itself, particularly .env.testing and .env.development.
edx-internal Addition
TODOTo add the new config value to the production configuration, the value must be added to the appropriate YAML file in the edx-internal repo. For example, this PR adds the new IGNORED_ERROR_REGEX value to the frontend-app-learning production configuration.
Deployment
How are MFEs prepared for - and operated in - a production environment?
...