the legacy frontend tooling in edx-platform is such a box of mysteries, at least to me
struggling to think of a way of avoiding pip install -e . from needing to be run when mounting edx-platform. I have some ideas but they all seem hacky (pip install -e . in an entrypoint script)
there might be a different form of pip install? bypassing the -e means we actually need a package proper to install
Regis: maybe have init scripts that run install -e that only run in development?
Working with a vendor (Verificient) who is having trouble in their integration environment with certain static assets (web workers out of an npm package) needed by proctoring, it seems they don’t get built into the image.
Meeting captain: Transpose action items into the “Action Item” section below.
Your Item of Success to Share
Suggested Action Items
@Rebecca Graber figure out why zach can’t edit/assign issues
Meeting captain: Move any remaining action item’s to next week’s minutes.