|Giuseppe Guerra 17ec65c07f Send backups in specified rsync path, not in full_backups subdirectory||2 years ago|
|.gitignore||3 years ago|
|LICENSE||3 years ago|
|README.md||3 years ago|
|backup.sh||2 years ago|
|config.sample.ini||2 years ago|
|sync.sh||2 years ago|
This simple set of bash scripts can sync Ripple replays, screenshots, avatars and database between different servers, so they’re safe in case the main server explodes.
sync.shsyncs Ripple’s data to another server. Only new or edited files get synced to the backup server.
backup.shcopies all data in a .tar.gz file, sends it to the backup server and, optionally, upload them to Backblaze and/or AWS S3.
We recommend running
sync.sh every 2 hours or so, and
backup.sh every week/month, depending on how large your ripple instance is.
config.ini and edit it. Main options:
backup.shwill sync/copy that data
db_*: MySQL credentials
*_folder: Folders containing ripple data
backblaze_*: Backblaze credentials. Optional. Leave everything empty to disable Backblaze upload
aws_*: AWS S3 credentials. Optional. Leave everything empty to disable S3 upload
local_folder: If not empty, all backups will be copied in that local folder. Optional. Leave empty to disable.
rsync_remote: Backup server’s rsync address. Used to sync data and send backups.
schiavo_url: Schiavo main URL. Optional. Leave empty to disable. Since schiavo is closed yource, you should keep this key empty.
All code in this repository is licensed under the GNU AGPL 3 License.
See the “LICENSE” file for more information