-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy OpenEdX Forum V2 to mitx #2894
Comments
Forked the repo and took a very uneducated swing at a Dockerfile, but I'm missing too much context for this to be a likely hit. |
Enabled in mitx-ci:
|
Enable mysql backend as per @blarghmatey:
|
From @blarghmatey: We need to provide the settings expected by the plugin which you can find at https://github.com/openedx/forum/blob/master/forum/settings/common.py In particular, we need to set the MongoDB values, as well as setting the search backend to forum.search.es.ElasticsearchBackend |
mongodb settings for forumv1: https://github.com/mitodl/ol-infrastructure/blob/main/src/bilder/images/forum/files/forum.env.j2 |
I figured out the necessary syntax for a couple of the configurables by interpolating the example found here: https://github.com/openedx/forum/blob/342ad3b59344cb998159eb4ee580b39785888a62/forum/settings/test.py#L68 with the forum v1 info Tobias pointed me at previously. Hopefully I managed to actually connect with the ball, if not make a base hit :) |
Where/how can I see this in action? Is it on https://lms-ci.mitx.mit.edu/ ? |
We found an upstream bug in validating this, reported at openedx/forum#155 |
Not even sure this will work going forward but worth a try. This is the URL that throws the exception: https://courses-qa.mitxonline.mit.edu/courses/course-v1:MITx+10.50.CH01x+1T2023/discussion/forum/ |
MITx Online QA. See my URL above for an exact path to reproduce, but I'm also not sure if that URL encodes my user etc as we went through a bunch of steps to get there. |
Description/Context
Overall
Changes that will require new infrastructure:
Deployment
The text was updated successfully, but these errors were encountered: