- release: Preparing 19.0.0
(
18af9e0
)
- Empty commit to trigger a version bump
(
5ae11a7
)
- release: Preparing 18.1.0
(
f91f939
)
- allow MFEs to be hosted on either the LMS or the CMS
Before all the MFEs that were hosted by path were hosted in the LMS domain. For certain MFEs (course-authoring) the CMS domain is more appropriate.
-
point the MFEs URLs to either the LMS or the CMS
-
handle special cases in the $LMS_HOST/account route.
The /account/password
endpoint is used in the 'forgot password' flow, for that reason we must
forward those requests to the LMS.
The /account/settings
is more specific to the multitenant use case. Some sites may be configured
to use the legacy pages but the current configuration would send every subpath of /account/
to
the MFE, we make an exception for the legacy URL.
This includes an additional executable script that is mounted to the MFE pod and is run at container startup time. The script replaces a placeholder string with the MFE_EXTENSIONS_CDN_URL setting.
- Add CDN support
(
c4ca397
)
This is the first exploration of CDN support for MFEs. We only support the default MFEs used in the Olive release and require a custom version of frontend-build and tutor-mfe.