![]() Your machine may hang here for a minute as git-annex waits for enough entropy to generate a key. $ git annex initremote b2 type =external externaltype =b2 accountid =xxxxxxxxxxxx \ appkey =xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx \ encryption =shared chunk =25MiB bucket =bgw-music I chose 25 MiB chunks, which seems like a good compromise. The documentation suggests a chunk size of 1 MiB as a starting point, but the because of how the b2 backend works, I find I get much better throughput with larger chunks. Git-annex has support for chunking, which allows for resumable uploads, and ensures things work smoothly if an excessively large file gets dropped in the repository. This stores the encryption key in the repository, but that’s not an issue, because we’ll be encrypting the non-annex portions of the git repository too. Bucket names that start with “b2-” are reserved for Backblaze use.įor encryption, I used the “shared” option. These are all allowed bucket names: myBucket, backblaze-images, and bucket-74358734. A bucket name must be at least 6 characters long, and can be at most 50 characters long. The name you pick must be a unique name that has not been used before, by you or by anybody else.īucket names can consist of upper-case letters, lower-case letters, numbers, and “-”. When you create a bucket, you get to pick the name for the bucket. Just understand the bucket naming restrictions: If you name a bucket that doesn’t exist yet, it’ll create one for you. Click on ‘My Account’ to get to the buckets list, where you can find your Account ID and Application Key Git-annex-remote-b2 needs your Account ID and Application Key, as well as a bucket name. I keep a bin directory in my $HOME for this purpose.Ĭonfiguration is slightly more complicated. ![]() ![]() Just download a binary, and toss it in your $PATH. $ git annex assistant Setting up git-annex-remote-b2 Fortunately, the NeuroDebian team maintains a frequently updated git-annex-standalone package. I’m on Debian stable, but I’m interested in some of the newer features of git-annex. Git-annex is available in the Debian repositories, which should come as no surprise, since Joey Hess, git-annex’s developer, was a Debian Developer until recently. Instead I’m using it as a secondary backup and for bit rot protection. In this case, I don’t care about using git-annex for syncing between devices, though I may later. I use beets to compress the music as ogg files before syncing it to my portable devices using rsync. I manage my music library on my desktop, which runs Debian Jessie. Optimal settings may vary based on total repository size, number of files, and the average size of files. This means the average file is 20-60 MiB in size, with some MP3s and other formats as outliers. I have 110 GiB of music, most of which is in flac format. I use beets to manage music metadata, and mpd to play my music. git-annex heavily modifies your working directory, and if something goes wrong, you could lose data. Disclaimersīefore attempting any of this, make sure you have a good backup of whatever you’re switching over to git-annex. recently wrote a ‘special remote’ backend for Backblaze’s ultra-cheap B2 storage API, so I figured it was time to give it a try. I’ve been interested in git-annex lately, as an offsite backup solution, a synchronization tool, and as a solution to bit rot. I have since switched to a combination of restic and syncthing. Update (2019): My requirements changed, and I no longer use this solution. Using git-annex to Mirror My Music Collection Using git-annex to Mirror My Music Collection - Benjamin Woodruff B.
0 Comments
Leave a Reply. |