![]() Afterwards I had to make sure that my keychain was available git-annex for a specific period of time. Generating a GPG key was the easiest step. create a special remote (see below) which offers encryption.In order to be able to encrypt my stuff before pushing into the cloud, I had to git commit -am initial repo On branch master Initial commit nothing to commit touch test.txt test.txt has a line. One the important constraints before pushing my backups into the cloud was security. You’ll have to work with git-annex to do that. That means: Newly added data (but not committed to the repo) can be deleted by the client which added the data. you can add files/folders and delete them only if these weren’t added to the git-annex repo yet.One can access the data using ownCloud but you there are some restrictions: The data itself is then managed by git-annex which basically acts as a back-end. OwnCloud will act as a front-end and can be used by any ownCloud client. It will then only contain the git information (symlinks) but no data (annexed data). From the server I could then replicate the repo+data stuff to some cloud provider like AWS, DropBox or whatever.Īdditionally one could push the git repo to GitHub in an encrypted form - without the data itself. Data is being encrypted using my private GPG key. Afterwards the encrypted repo and the data itself is being pushed to some external server. Usually I push stuff to the HDD using rsync from my laptop or ownCloud using my mobile clients. For a list of available backends, see git-annex version. A single repository can use different backends for different files. Most backends are different kinds of hashes. For a list of available backends, see git-annex version. The 'backend' in git-annex controls how a key is generated from a file's content and/or filesystem metadata. There is one centralized repo on my raspberry pi where my HDD is attached to. The 'backend' in git-annex controls how a key is generated from a files content and/or filesystem metadata. While this might sound like a pretty easy task, it does have some peculiarities to be taken into consideration. Well this post is where the link between git-annex and ownCloud should be emphasized: Use ownCloud as your “frontend” tool for accessing the data while letting git-annex do the “backend” (aka backup) job. In connection with a VPN (I prefer openvpn) solution you can have a secure way of remotely accessing your data from everywhere. Meanwhile I’ve heard of ownCloud and I’ve liked it because one can access its data via web, mobile client or whatever. I’ve been using git-annex for some years but not like a pro user, rather than “it just works”. Besides that you don’t want to have your backups at a single place, thus mitigating the impact of a single point of data loss. Taking care of the consistency of your backups is even more complicated task. ![]() For finer control of what backend is used when adding different types of files, the. The first one listed will be used by default when new files are added. Backuping a whole bunch of photos and videos might be a difficult task. The annex.backends git-config setting can be used to list the backends git-annex should use.
0 Comments
Leave a Reply. |