-
Notifications
You must be signed in to change notification settings - Fork 15
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
[Tutor] Document migration from native installation #78
Comments
One Tutor user already made a lot of research on this particular topic: https://discuss.overhang.io/t/migrating-from-native-install-to-tutor-juniper-tutor-10-x/1533 |
@BbrSofiane did you make progress on this? |
@regisb I have a set of notes that I need to clean up and write somewhere. This shouldn't take me more than a couple of hours. |
Famous last words 😉 No but seriously, I'm glad that you tackled this. |
Indeed 😂 |
Hello @BbrSofiane, do you consider that we need to document more details about this process?Thank you so much |
@NeOneSoft I think the document provides a good starting point. Going forward it can be improved based on feedback from people using it. I'm happy to close the issue unless there are additional comments, |
@BbrSofiane thank you so much for you response!!. If you are agree and there's no additional comments you can go ahead. Thanks again!! |
As described in Criterion 6 of OEP-45, ADR-1, the community needs a documented way to migrate from the now deprecated native installation into a Tutor-deployed one.
Given the current timeframe, this documentation should target a migration from edx/configuration@lilac.X to tutor@maple.1.
The text was updated successfully, but these errors were encountered: