Trouble mounting tutor-mfe: frontend-app-authoring

Hello everyone,

I have been trying to mount frontend-app-authoring to my tutor. Here is what I have done:

  1. Cloned frontend-app-authoring to my local machine and made a very basic change to the code. I made the background of the mfe ‘black’ and saved the code.

  2. I then ran the tutor’s mounting command which successfully mounted the cloned repo to tutor. I then ran tutor dev launch but the changes I made to the code i.e., made background black isn’t being reflected.

  3. When this didn’t work, I also tried running the authoring mfe locally and every other service (cms, lms, mfe) in the container (Followed steps mentioned here. The authoring mfe runs on port 2001 but I get some authentication error which doesn’t let me go into the studio.

Any help will be greatly appreciated!

What version of the tutor-mfe plugin are you running? This issue should have been fixed in 18.1.0.

What is the output of tutor mounts list?

tutor, version 18.1.3.

output of tutor mounts list:

- name: /home/suleman/out_of_root/frontend-app-authoring
  build_mounts:
  - image: mfe
    context: authoring-src
  - image: authoring-dev
    context: authoring-src
  compose_mounts:
  - service: authoring
    container_path: /openedx/app

Thank you for your reply. Can you also tell me what is the recommended way of mounting and launching tutor-mfe plugins? Is it 2. or 3. in my original post or are both methods okay? Thanks, again.

Also, I just realised you are asking about tutor-mfe version. When I ran tutor plugins list, I got this:

mfe :white_check_mark: enabled 18.0.1

Do you think this could be the issue?

I have updated it to 18.1.0 and repeated this step:

I then ran the tutor’s mounting command which successfully mounted the cloned repo to tutor. I then ran tutor dev launch but the changes I made to the code i.e., made background black isn’t being reflected.

No luck. Changes were not reflected.

Your approach is correct: tutor mounts add ... && tutor dev launch.

Is the authoring container running? (docker ps | grep authoring)

Are your changes reflected in that container? (tutor dev exec authoring && cat ...)

Authoring container is not running I believe. I ran tutor mounts path/to/frontend-app-authoring followed by tutor dev launch. Tutor mounts list shows that frontend-app-authoring has been mounted as shown in 2/7 of this thread. Attaching an image of the output of docker ps. I cannot see authoring here.

My bad, the course-authoring rename was only made in the nightly/main branch, not the master/release branch: feat: rename "course-authoring" MFE to "authoring" by regisb · Pull Request #225 · overhangio/tutor-mfe · GitHub

Thus, to mount your authoring repo, you should rename the directory to frontend-app-course-authoring.

1 Like

Oh, wow. Thanks a lot for your help. I’ll try this out soon and let you know. Should probably work now.

Okay so this worked. I have mounted it and the background color changes are being reflected on app.local.edly.io:2001/course-authoring since I changed index.scss in the src folder. However, I have ran into another issue. I have created a superuser using tutor but whenever I login to studio using that account, it takes me to app.local.edly.io:2001/course-authoring/home. As soon as I login, I get this axios error in the image attached. It does run for a split second where I can see the studio home but then I get the error screen. The only error I can see in the network tab has something to do with course waffle flags and analytics.min.js as shown in the image

Thanks a lot for your time, I am truly grateful

I don’t know how to solve that one. I suggest you try it out first without bind-mounting your repo. If you are able to authenticate without bind-mount, but it fails with bind-mount, then you have an issue. That issue will be different than the one that you initially reported, so I suggest you open a new topic.

Yeah it works without mounting my repo. I’ll open a new topic for that. Thanks a lot for your help and patience, Regis. Means a lot.