I have been trying to mount frontend-app-authoring to my tutor. Here is what I have done:
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.
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.
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.
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.
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.
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.
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
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.