2022-10-19 DevEnv Meeting Notes
Date
Oct 19, 2022
Participants
@Rebecca Graber (Deactivated)
@Kyle McCormick
@Zach Hancock (Deactivated)
@Jeremy Bowman (Deactivated)
@Connor Haugh (Deactivated)
Goals
Discussion topics
Time | Item | Presenter | Notes |
---|---|---|---|
| Updates | All | Becca:
Connor: Maybe as soon as the end of the month!
Jeremy:
Kyle:
|
Development environment first principles | @Jeremy Bowman (Deactivated) | Working on a doc to solidify what we’re trying to accomplish with our development environment, to guide specific technology choices and improvements prioritization. Notes: Every time we start talking about DevEnv related things, there’s a lot of confusion about where we are, what are the priorities, who is doing what, and what do we actually want Fleshing out the existing doc that has some goals briefly stated using info from talking to others If we have reasonable consensus on ^, we can get more technical Development Environment Vision Folks can add comments to the doc or on the DevEnv thread | |
| Quickdev! It’s like dev, but quicker | @Kyle McCormick | Plugin:
Goal: improve basic edx-platform development Tool: Docker named volumes Hoping to propose this plugin to be merged into Tutor core Problem: Using one’s own copy of edx-platform means installing requirements, doing scary npm/paver things, and messing it up can mean everything is terrible. Also have to store local copies of any plugins in development deep in your Tutor config folder Why? Edx-platform’s setup.py needs to be run in order for plugins to be used. This creates a .egg-info file that’s within the repository (overwriting what Tutor had in there). Same with npm_modules and the static folders. Named volume: something that is stored by Docker outside of containers that sticks around between container restarts The plugin uses named volumes to store npm_modules and static assets when they were populated from the Docker image Also automatically mounts prefixed-plugins/xblocks to the right place |