We are working with a Tutor-based installation and we tried to install Proctortrack as a proctoring tool in our platform(Koa version), but we had an issue with the assets of the tool that are not being compiled. We also check that in the Tutor installation they don’t have it contemplated.
Do you know how we can do it to compile these assets separately?
We check the Dockerfile and we noticed that to collect static assets, it runs the commands individually with “openedx-assets” instead of using “paver update_assets”. The issue we have is that we don’t really identify the path or module where ProctorTrack assets can be compiled with this approach.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.