Add Steps to Generate Ratings, update disaster recovery docs
#87
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ajmosca
reviewed
Jun 20, 2025
SourMongoose
approved these changes
Jun 20, 2025
ajmosca
approved these changes
Jun 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a "Steps to Generate Ratings" guide. This guides users through database setup & import, otr-processor execution, and how to export the data into CSV files. Some basic troubleshooting steps are added to aid users in the event of any issues. Article instructs users on how to filter for specific osu! IDs.
Disaster recovery steps now reflect our new database import process (staging/prod use the 'otr-scripts' repo for this). Developers/those following the steps to generate ratings article can now import their database in one line. The command automatically overwrites the existing database instance - no need to drop and recreate the public schema anymore.
Closes #54