Merge branch 'master' of ssh://git-annex.branchable.com

This commit is contained in:
Joey Hess 2013-05-27 19:41:55 -04:00
commit 0ab9b9d0db
5 changed files with 74 additions and 0 deletions

View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawmUJBh1lYmvfCCiGr3yrdx-QhuLCSRnU5c"
nickname="Justin"
subject="comment 4"
date="2013-05-27T22:24:44Z"
content="""
> If you're up for testing a patch, I could do it today.
I'm happy to test a patch. I haven't successfully compiled git-annex on my Mac, which is the only computer I have for the next month or so, but it wasn't too hard to get it to work on my Linux box.
"""]]

View file

@ -0,0 +1,12 @@
[[!comment format=mdwn
username="http://joeyh.name/"
nickname="joey"
subject="comment 3"
date="2013-05-27T19:14:37Z"
content="""
I am confident that it will be *easier* to install git-annex-shell on your ssh server than it will be to lock down rsync.
All you need to do is go get the standalone linux tarball of git-annex, untar it, and add its directory to PATH.
You can google for perl scripts that lock down rsync, but I have never been happy with any of the ones I found.
"""]]

View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="http://joeyh.name/"
nickname="joey"
subject="comment 2"
date="2013-05-27T18:47:17Z"
content="""
You can also use `git annex reinject` to feed in contents of specific files, without needing to directly touch the files in the repository.
Or, you can check all the local files into a temporary directory. Either the assistant or a manual `git annex add` will
notice if these files have the same content as files already in the repository. The files will then be available in two locations, the temp directory and wherever it was checked into your repository before. You can then delete the temp directory.
"""]]

View file

@ -0,0 +1,12 @@
[[!comment format=mdwn
username="http://joeyh.name/"
nickname="joey"
subject="comment 1"
date="2013-05-27T19:09:50Z"
content="""
Mega can be used via [[/tips/megaannex]]. I don't have personal experience with it, but if you set up a repository manually using that, the assistant can use that repository just as it uses any other repository.
git-annex at the command line is great for small local repositories that pull files from various larger remotes as needed. You just run \"git annex get\" when you want a file and \"git annex drop\" when you want to free disk space. You can also use this mode with the assistant, by configuring the local repository to be in \"manual mode\".
By default though, the way the assistant handles this kind of use case is with `archive` directories. It tries to move any files in an archive directory away from your local disk, and it tries to get any files not in an archive directory to be locally available. So you can just move files around between directories to control where they are stored. See [[assistant/archival_walkthrough]] for details an an example video.
"""]]

View file

@ -0,0 +1,29 @@
skydriveannex
=========
Hook program for gitannex to use skydrive as backend
# Requirements:
python2
python-yaml
Credit for the Skydrive api interface goes to https://github.com/mk-fg/python-skydrive
# Install
Clone the git repository in your home folder.
git clone git://github.com/TobiasTheViking/skydriveannex.git
This should make a ~/skydriveannex folder
# Setup
Run the program once to set it up.
cd ~/skydriveannex; python2 skydriveannex.py
# Commands for gitannex:
git config annex.skydrive-hook '/usr/bin/python2 ~/skydriveannex/skydriveannex.py'
git annex initremote skydrive type=hook hooktype=skydrive encryption=shared
git annex describe skydrive "the skydrive library"