Closed ericfab179 closed 4 years ago
Should the custom_reports be a separate git repo that we include into edx-platform via pip (or some other approach)? I'm thinking about our future plans to migrate to Hawthorn/Ironwood/Juniper
Should the custom_reports be a separate git repo that we include into edx-platform via pip (or some other approach)? I'm thinking about our future plans to migrate to Hawthorn/Ironwood/Juniper
@ryangadams Yes maybe another approach is better. @andrey-canon could it be a pulgin ?
Should the custom_reports be a separate git repo that we include into edx-platform via pip (or some other approach)? I'm thinking about our future plans to migrate to Hawthorn/Ironwood/Juniper
@ryangadams Yes maybe another approach is better. @andrey-canon could it be a pulgin ?
@ryangadams @ericfab179 yeah, this should be a plugin in order to make the migrations easier, but first we should test if the plugins works right on this platform version and then re-factor the app.
Ok, here's what I'm going to ask Zeus to change and re-submit:
I'm not going to request shifting to celery or a plugin, but we might need to consider that approach in future.
This PR adds the djangoapp "custom_reports" developed by Zeus Learning for edx-platform.