Introduce a background synchronization layer between Catalog and LMS that populates the data within the CourseOverviews sql table.
Design document is located here: https://openedx.atlassian.net/wiki/display/MA/Course+Sharing+Design+Thoughts
We have decided to break this into 4 sub-tasks:
Introduce marketing_url in CourseOverview model and create simplest mgmt. command for CMU synchronization
Update get_lms_link_for_about_page to return course_overview.social_sharing_url or course_overview.marketing_url or reverse('about_course', args=[course_overview.id]). And it's usage in platform
Use create_or_update logic instead of deletion and recreation upon course publish
Figure out the way to handle CCX courses (not having enough knowledge about it, need to groom this)
Right now, I am setting up docker for course-discovery. In parallel, I've started working on #1 sub-task. I haven't tested it yet as I am not having local setup. Still the initial WIP PR is https://github.com/edx/edx-platform/pull/14510 – It'd be great if can get initial feedbacks on it.
FYI , , .
Do you think #2 is necessary before #3? I believe #1 and #3 are the minimal necessary to provide value-add to the users. After which, the mobile team can start enabling the Course-Sharing feature.
#2 may be more involved and can come afterwards. Same with #4.
I agree, #1 and #3 would make this functional at least. I thought the same, but miss-ordered while making comment, swapping #2 and #3
Currently, I am setting up whole devstack via Docker locally (following: https://github.com/edx/devstack/blob/master/README.md). Previously, I was unable to communicate from docker container running catalog service to vagrant machine running edx-plaftorm (issue was: http://127.0.0.1:8000/oauth2/ was not browse-able inside docker container, I think its related to port forwarding).