To use Tutor in a production env in eduNEXT we use manifest and a tool called Shipyard, and with that, we use ArgoCD. I can bring more details at the next meeting, but I think a college will discuss it at the conference. Shipyard: https://github.com/eduNEXT/shipyard
Related to my “challenge” below… i’m going to be putting together a tCRIL-funded project pitch to finish where BD-39 started (upgrading react, paragon, libsass, etc. in edx-platform)
I’m interested in removing the Python from the edx-platform build pipeline. ADR to come.
Each challenge should have a follow up action.
If you have an idea for follow up actions, add it.
Or if you aren’t sure, leave it blank.
We’ll discuss all actions either way.
Your Item of Challenge to Share
Idea for Follow Up Action
Attempting to use tutor for tutor dev and devstack for feature development on the same machine
+1 from Becca
Idea for Follow Up Action: using hosted devstack now, which frees up my local machine to run tutor
Many edx-platform frontend frameworks are still way out of date: in particular, libsass and paragon. This was hard for me because it means that we can’t use newer Sass compilation tools (node-sass or dart-sass) which would simplify our asset pipeline.
Some simplifications to Tutor’s tutor.hooks API coming soon – goal is less confusion between different ways of calling the API ("cli:jobs" vs. CLI_JOBS, etc)
Very high latency in PR reviews across team boundaries