Set of scripts generating SQL and .osu dumps from production for osu-performance developers to use locally.
These scripts are for internal use only. Please find the dumps on https://data.ppy.sh.
Run ./dump_all.sh
monthly with the following environment variables:
- beatmaps S3 bucket:
OSU_DOWNLOAD_AWS_ACCESS_KEY_ID
,OSU_DOWNLOAD_AWS_SECRET_ACCESS_KEY
,OSU_DOWNLOAD_S3_BUCKET
,OSU_DOWNLOAD_S3_ENDPOINT
- data.ppy.sh S3 bucket:
DUMPS_UPLOAD_AWS_ACCESS_KEY_ID
,DUMPS_UPLOAD_AWS_SECRET_ACCESS_KEY
,DUMPS_UPLOAD_S3_BUCKET
,DUMPS_UPLOAD_S3_ENDPOINT
,DUMPS_UPLOAD_S3_ACL
(optional) - osu! database:
DATABASE_HOST
,DATABASE_USER
,DATABASE_PASSWORD
(optional)
For DigitalOcean Spaces support, DUMPS_UPLOAD_S3_ENDPOINT
and DUMPS_UPLOAD_S3_ACL
need different values, eg DUMPS_UPLOAD_S3_ENDPOINT=https://nyc3.digitaloceanspaces.com
and DUMPS_UPLOAD_S3_ACL=public-read
.
For s3-nginx-proxy purge support, DUMPS_UPLOAD_S3_PUBLIC_URL
and DUMPS_UPLOAD_S3_PURGE_AUTHORIZATION_KEY
need to be set (optional).
~16GB of free disk space is recommended (estimated).
Contributions can be made via pull requests to this repository. We hope to credit and reward larger contributions via a bounty system. If you're unsure of what you can help with, check out the list of open issues.
Note that while we already have certain standards in place, nothing is set in stone. If you have an issue with the way code is structured; with any libraries we are using; with any processes involved with contributing, please bring it up. I welcome all feedback so we can make contributing to this project as pain-free as possible.
The osu! client code, framework, and server-side components are licensed under the MIT licence. Please see the licence file for more information. tl;dr you can do whatever you want as long as you include the original copyright and license notice in any copy of the software/source.
Please note that this does not cover the usage of the "osu!" or "ppy" branding in any software, resources, advertising or promotion, as this is protected by trademark law.