How to use learning MFE on tutor

sumanchapai · August 4, 2021, 4:52pm

I see that learning MFE isn’t available by default in the latest release (V 12.0.2). But is there a way to use that MFE? I see that edx.org is using it… and maybe there is a way to use that on tutor too?

regis · September 1, 2021, 1:32pm

Hi @sumanchapai! You could try to enable the learning MFE by extending the existing MFE plugin, following these instructions: GitHub - overhangio/tutor-mfe

Note that I’ll be working on getting the learning MFE working on the master branches of Open edX in the coming weeks. I’m pretty sure that the learning MFE will not work out of the box in the Lilac release, though…

sumanchapai · September 26, 2021, 5:29am

Hello @regis , thank you for your reply.

I am recently looking into adding a learning MFE in the site by just using a yml plugin. But it seems like I would have to set the redirects and set ENABLE_LOGIN_MICROFRONTEND like it’s done in the tutor-mfe for profile mfe

github.com

overhangio/tutor-mfe/blob/4713862d5e7e2774e7a3348c2237994c9b61efeb/tutormfe/templates/mfe/hooks/lms/init

{% if MFE_ACCOUNT_MFE_APP %}
(./manage.py lms waffle_flag --list | grep account.redirect_to_microfrontend) || ./manage.py lms waffle_flag --create --everyone account.redirect_to_microfrontend
{% else %}
./manage.py lms waffle_delete --flags account.redirect_to_microfrontend
{% endif %}

{% if MFE_PROFILE_MFE_APP %}
(./manage.py lms waffle_flag --list | grep learner_profile.redirect_to_microfrontend) || ./manage.py lms waffle_flag --create --everyone learner_profile.redirect_to_microfrontend
site-configuration set ENABLE_PROFILE_MICROFRONTEND true
{% else %}
site-configuration unset ENABLE_PROFILE_MICROFRONTEND
./manage.py lms waffle_delete --flags learner_profile.redirect_to_microfrontend
{% endif %}

But I see that this is done in hooks, and I am unsure if this can be added in the yml file too. If else would I have to make a plugin using something like the cookiecutter?

I also wanted to ask, and I think it’s a good time and place, where are the git repos stored that we clone when installing mfes or other things? So that when if I write a plugin using cookiecutter, I can delete the previously cloned repo and only use the new copy or reuse this…

Thank you for your response.

regis · September 27, 2021, 5:18am

This is correct. Hooks require templates, which are not supported by the YAML plugins API, so you will have to create a python plugin using the cookiecutter.

Now that I think of it, it does not make much sense to load hooks from templates. They should be declared as raw strings, pretty much like the patches from a plugin are loaded from disk… I created an issue: Plugin hooks are not supported by the yaml plugin API · Issue #499 · overhangio/tutor · GitHub

The MFEs are cloned in the mfe container, in /openedx/app. But these folders are not accessible at runtime because we use multiple Docker layers in our mfe image: tutor-mfe/tutormfe/templates/mfe/build/mfe/Dockerfile at master · overhangio/tutor-mfe · GitHub

system · December 26, 2021, 5:19am

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.