Inconsistent MFE URL configs between local and production environments (<domain> vs <domain>/<mfe>)

Development
1

Currently, during local development, the API http://apps.local.openedx.io:2001/api/mfe_config/v1?mfe=authoring returns a configuration with the following values:

ACCOUNT_PROFILE_URL: "http://apps.local.openedx.io:1995/profile"

ACCOUNT_SETTINGS_URL: "http://apps.local.openedx.io:1997/account/"
...
LEARNING_BASE_URL: "http://apps.local.openedx.io:2000"

This means we have correct links for the Profile and Account MFEs (<domain>/<mfe>), but an incorrect one for the Learning MFE, where only the domain is provided without the MFE ID.

This issue becomes noticeable on the Pages & Resources page in the Authoring MFE. The View live button contains a link like:

href="``http://apps.local.openedx.io:2000/course/course-v1:openedx+123+2024``"

This URL points to a non-existent page in the Learning MFE, because the expected /learning ID is missing after the domain.

I believe this inconsistency should be addressed. All MFE URLs should follow a unified <domain>/<mfe> structure to ensure correct routing both locally and in production. The current LEARNING_BASE_URL value is just one example that highlights the problem, and similar issues may arise with other MFEs if the configuration is not standardized.

2

@arbrandes @brian.smith

3

Is 2000 intentional here, or should it be 2001?

I’m seeing /learning locally from http://apps.local.openedx.io:2001/api/mfe_config/v1?mfe=authoring:

"LEARNING_BASE_URL": "http://apps.local.openedx.io:2000/learning",
4

Is 2000 intentional here, or should it be 2001?

Yes, fixed

I’m seeing /learning locally from http://apps.local.openedx.io:2001/api/mfe_config/v1?mfe=authoring

Have you overridden LEARNING_BASE_URL via MFE_CONFIG_OVERRIDES?

5

I have not.

6

Recently, changes were introduced that address this issue in the Learning MFE.