-
Notifications
You must be signed in to change notification settings - Fork 56
[Documentation:Developer] Reorganize troubleshooting #565
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
Conversation
Nicc041
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything works and the code looks good.
benlee04
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code seems fine and works.
bmcutler
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggested undoing some of the shuffling
|
|
||
| --- | ||
|
|
||
| ## System Clock Testing & Troubleshooting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i agree with moving the system clock troubleshooting to another file
|
|
||
| --- | ||
|
|
||
| ## System Re-Configuration |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but the instructions for teting changes to configure_submitty.py & etc should stay here
|
|
||
| --- | ||
|
|
||
| ## Re-Creating All Sample Course Data |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and the instructions for rebuilding sample course data should stay here
|
|
||
| --- | ||
|
|
||
| ## Complete System Re-Installation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and system re-installation instructions should stay here
|
|
||
| See also: [Re-Creating All Sample Course Data](/developer/development_instructions/index#re-creating-all-sample-course-data) | ||
|
|
||
| See also: [Re-Creating All Sample Course Data](/developer/troubleshooting/reinstallation_troubleshooting) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so we will revert this change
| @@ -0,0 +1,97 @@ | |||
| --- | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this shouldn't be a separate page, its not troubleshooting, they are development instructions (less commonly used, but still development instructions)
navtreedata.js
Outdated
| ] ], | ||
| [ "Troubleshooting & Other Information", "/developer/troubleshooting/installation_troubleshooting", [ | ||
| [ "Installation", "/developer/troubleshooting/installation_troubleshooting", null ], | ||
| [ "Re-Installation", "/developer/troubleshooting/reinstallation_troubleshooting", null ], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this goes away
Reorganized the troubleshooting pages under developer. Organized troubleshooting into 3 files (Installation troubleshooting, Re-installation troubleshooting, and System Clock Testing & Troubleshooting). Now developers can go to the new troubleshooting folder to find instructions on how to fix their problem.