Please familiarise yourself with the forum, including policy on feature requests, rules & guidelines

Using Github to backup your XML files for kits, songs, and synths.

6
alifeinbinaryalifeinbinary Vancouver, CanadaBeta Tester Posts: 10

I was periodically backing up my SD card to my Dropbox but found the process to be cumbersome, since I only wanted to update the songs/synths/kits that had changed since the last backup instead of overwriting everything. Then I had the idea to use git to backup the XML files in the KITS/ SYTHNS/ and SONGS/ directories, since git is made for doing exactly this. I created a .gitignore file to ignore the /SAMPLES/ directory (this still gets stored on Dropbox/Nextcloud) and any hidden files the Deluge creates.

.gitignore:
/SAMPLES/*
.*

This is a much better solution as it saves a lot of time and worry during backup. Having version control for your sounds and songs is ideal in the event that you want to return to a previous version down the road. You could maintain separate branches for [production], [live] etc. Anyway, just thought I would share. Also, take this as a friendly reminder to backup your data!

Post edited by alifeinbinary on

Comments

  • 0
    HeptagenHeptagen Posts: 105

    Very good idea, thanks!

  • 0
    phillipadsmithphillipadsmith United StatesPosts: 37

    Smart!

  • 0
    ceetronicceetronic Chepstow, South Wales, UKPosts: 19

    Great idea!

  • 0
    neilbaldwinneilbaldwin UKPosts: 135

    Love this, great idea!

  • 1
    musirafaelmusirafael madridPosts: 9

    Seems like a good idea! Just make it a private repository if you have bought commercial presets.

    I wonder why the community have not produced a central repository for free patches in GitHub with a common agreed directory structure.

  • 0
    BolganiBolgani SuomiPosts: 28

    Took a look at this out of curiosity. It seems that GitHub has some public synth patch storages and I was wondering what this would take to create a public repository:

    • The repository itself (meh)
    • Probably the best course of action would be that a someone or preferably a group of people would manage this and take contributions by email/whatever and download them to the repository.
    • The alternative would be that the contributors must have a GitHub account and a Contribution right to the repository and should push branches of their changes and someone would have to review and approve them and I'm afraid that it would get rather confusing for some. GitHub is tool made for coding and has it's own workflow suited for that environment.

    But I think that the main problem is that it seems GitHub recommends repositories to be under 1GB or at least 5GB. Which would store a very large coding project but we have samples. In comparision Google Drive offers 15GB free for an account. Don't know then. :|

  • 1
    alifeinbinaryalifeinbinary Vancouver, CanadaBeta Tester Posts: 10

    I'm not advocating that anyone store the /SAMPLES/ directory within a git repository for the same reason you mentioned, it will balloon in size. I backup /SAMPLES/ separately in my Dropbox. Everything else is text-based in XML format, so git works perfectly. As for the idea of maintaining a public repo for non-commercial Deluge patches, it could work. You're right, people who want to contribute would need to be familiar with the git workflow and commands in order to simplify the maintainance of said project. In order to manage all the sounds, Rohan may need to implement a sub-directory functionality for /SYNTHS/ so it could be further split up into sub-categories like /SYNTHS/PADS/, /SYNTHS/LEADS/, etc. This functionality may be in the development pipeline anyway.

Sign In or Register to comment.