Recent comments posted to this site:
Is there a way to estimate the cost of storing a repo on glacier?
I'm especially worried because of the cost of STORE and RETRIEVE requests; there are hundreds of thousands of small files in my annex repo, so that request cost could easily dominate storage cost. Does the glacier remote do anything to minimize the number of objects stored in glacier?
By default, git annex sync
will sync to all remotes, unless you specify a remote. So, I have to specify, e.g., git annex sync origin
. I can simplify this with aliases, I suppose, but I do a lot of teaching non-programmer scientists... so it'd be nice to be able to configure this (so beginning users don't have to keep track of as many things).
Is there (or will there be) a way to do this?
@Bence the closest I have is some tests of particular special remotes inside Test.hs. The shell equivilant of that code is:
[[!format sh """ set -e git annex copy file --to remote # tests store git annex drop file # tests checkpresent when remote has file git annex move file --from remote # tests retrieve and remove """]]
Is there a unit test or integration test to check for the behavior of a special remote implementation and/or validity?
I don't speak Haskell, so maybe there are some in the source but maybe I wouldn't recognize, so I haven't checked. If there are any tests how should I use it?
Thank you, Bence
Hey,
You don't have to implement any whacky DMG replacement logic for OSX upgrades. No sane user will be using the application from the DMG. They will drag the .app directory to /Applications or some non-standard location and unmount the DMG. So your upgrade logic for OSX should end up looking very similar to the upgrade logic for Linux.
my gitolite.rc is available at https://gist.github.com/khaije1/7609848
For whatever reason I've found this to be very simple to get working so I'd guess there's a missing ingredient somewhere. The combination of gitolite and git-annex is valuable to me so I'll add documents to the url above in hopes it will assist some people with getting the same value.
To make XMPP via a Google Apps account work out of the box, all you need to do is add the correct SRV records to your domain's DNS zone. If you do, you don't need to manually create creds/xmpp, you can just use the web interface, enter your full apps email address and password (remember, if 2-factor, this needs to be an application-specific password).
To create the correct SRV records (and check whether they're correct), see http://www.olark.com/gtalk/check_srv