Closed OmarIthawi closed 4 years ago
@thraxil @johnbaldwin FYI.
@OmarIthawi Looks very reasonable. We can then use repo deploy keys and store the required keys in each edx-config installation's secrets.yml file
I would LOVE to no longer have to use homerbot, too!
Thanks for writing this up!
I no longer think of this as an issue since we don't overuse privage git requirements.
The Problem
We can't use the same SSH key for checking out multiple private git repositories on GitHub. Therefore we don't know how make Open edX install private git repositories via pip in a clean way.
The current method of requirements is to make the whole edX Platform installation to use a HomerBot key which needs decent amount of manual work and pinging others for something that should be simple.
Proposed Solution
I propose making a role for installing requirements for the Open edX, or pretty much any virtual env.
Technical Details
So our solution is to first clone those requirements into a directory, then instruct pip to get that directory.
The role configs would look like the following:
The role would roughly do the following:
Let's retire @HomerBot!