git-annex-remote-hubic | annex special remote for hubiC -- UNMAINTAINED | Continuous Backup library

Install Python3 and setuptools ≥ 0.7 (on Arch Linux: pacman -S python-setuptools; on Debian/Ubuntu: apt-get install python3-setuptools). If setuptools ≥ 0.7 is not available, you can install distribute instead; if distribute isn’t available either, you should try to install setuptools in your $HOME with pip3 install --user --upgrade setuptools.
Install Python3 and setuptools ≥ 0.7 (on Arch Linux: pacman -S python-setuptools; on Debian/Ubuntu: apt-get install python3-setuptools). If setuptools ≥ 0.7 is not available, you can install distribute instead; if distribute isn’t available either, you should try to install setuptools in your $HOME with pip3 install --user --upgrade setuptools.
Clone this repository: git clone git://github.com/Schnouki/git-annex-remote-hubic.git
Install the package: python3 setup.py install --user
Go to a repository you manage with git-annex, and initialize your new remote using the following commands as a starting point: git annex initremote my-hubic-remote type=external externaltype=hubic encryption=shared hubic_container=annex hubic_path=path/to/data embedcreds=no my-hubic-remote is the name of your remote hubic_container is the name of the Swift container used to store your data. If you don’t specify anything, the name "default" will be used, which is the name of the container used by the hubiC desktop client and shown in the web interface. Therefore it is not recommended to use the "default" container to store your annexed data, as they will be synced to your computer if you use the desktop client. hubic_path is the directory where your annexed data will be stored in the container your chose. embedcreds controls whether your access token shall be stored in the git repository. If set to yes, anyone with access to your repository can get full access to all your hubiC data, so don’t set it to yes unless you really trust the machines where your repository is stored and the people who have access to it. encryption is used to control whether your data will be encrypted on the remote, just like with [any other remote](http://git-annex.branchable.com/encryption/).
The very first version of this remote, when published to GitHub, only supported storing data in the default container. However doing so is not recommended as data stored in that container will be synced to your computer if you use the desktop client.