Description
Create a plugin to tutor-mfe that allows operators to select whether a given MFE will be deployed as an SPA or as a frontend-base app.
Requirements
- Upon a rebuild of the mfe image, includes both MFE and frontend-base build artifacts. It does not remove any existing MFEs, just adds the frontend-base ones.
- Exposes
site.config in a similar way to how env.config.jsx is exposed today.
- Modifies Django config so that the frontend-base in question is used by default when enabled.
- Modifies
site.config's roles and external URLs so that they link out correctly to SPA MFEs when they're not in frontend-base mode.
In addition, in dev mode it should be possible to easily disable the frontend-base site's port binding in a way similar to how bind-mounting an MFE and not starting its dev image does it. This is so it'll possible to develop frontend-base MFEs by running npm run dev outside the Tutor Docker container, but still having it work.
Finally, we're tacking on the proposed tutor-googleanalytics plugin as a sub-issue here, too.
Description
Create a plugin to tutor-mfe that allows operators to select whether a given MFE will be deployed as an SPA or as a frontend-base app.
Requirements
site.configin a similar way to howenv.config.jsxis exposed today.site.config's roles and external URLs so that they link out correctly to SPA MFEs when they're not in frontend-base mode.In addition, in dev mode it should be possible to easily disable the frontend-base site's port binding in a way similar to how bind-mounting an MFE and not starting its dev image does it. This is so it'll possible to develop frontend-base MFEs by running
npm run devoutside the Tutor Docker container, but still having it work.Finally, we're tacking on the proposed tutor-googleanalytics plugin as a sub-issue here, too.