2012-05-28 18:41:23 +00:00
|
|
|
The [[syncing]] design assumes the network is connected. But it's often
|
|
|
|
|
not in these pre-IPV6 days, so the cloud needs to be used to bridge between
|
|
|
|
|
LANS.
|
|
|
|
|
|
|
|
|
|
## more cloud providers
|
|
|
|
|
|
2012-05-29 23:17:38 +00:00
|
|
|
Git-annex already supports storing large files in
|
|
|
|
|
several cloud providers via [[special_remotes]].
|
2012-05-28 18:41:23 +00:00
|
|
|
More should be added, such as:
|
|
|
|
|
|
2012-05-28 18:47:16 +00:00
|
|
|
* Google drive (attractive because it's free, only 5 gb tho)
|
|
|
|
|
* OpenStack Swift (teh future)
|
2012-05-28 18:41:23 +00:00
|
|
|
* Box.com (it's free, and current method is hard to set up and a sorta
|
2012-05-28 18:47:16 +00:00
|
|
|
shakey; a better method would be to use its API)
|
|
|
|
|
* Dropbox? That would be ironic.. Via its API, presumably.
|
2012-09-04 18:58:11 +00:00
|
|
|
* [[Amazon Glacier|todo/special_remote_for_amazon_glacier]]
|
2012-09-21 23:19:15 +00:00
|
|
|
* [nimbus.io](https://nimbus.io/) Fairly low prices ($0.06/GB);
|
|
|
|
|
REST API; free software
|
2012-05-28 18:41:23 +00:00
|
|
|
|
2012-09-23 19:15:01 +00:00
|
|
|
## The cloud notification problem
|
2012-05-28 18:41:23 +00:00
|
|
|
|
2012-09-23 19:15:01 +00:00
|
|
|
Alice and Bob have repos, and there is a cloud remote they both share.
|
|
|
|
|
Alice adds a file; the assistant transfers it to the cloud remote.
|
|
|
|
|
How does Bob find out about it?
|
2012-05-28 18:41:23 +00:00
|
|
|
|
2012-09-23 19:15:01 +00:00
|
|
|
There are two parts to this problem. Bob needs to find out that there's
|
|
|
|
|
been a change to Alice's git repo. Then he needs to pull from Alice's git repo,
|
|
|
|
|
or some other repo in the cloud she pushed to. Once both steps are done,
|
|
|
|
|
the assistant will transfer the file from the cloud to Bob.
|
2012-05-29 23:17:38 +00:00
|
|
|
|
2012-10-01 15:30:51 +00:00
|
|
|
* dvcs-autosync uses jabber; all repos need to have the same jabber account
|
|
|
|
|
configured, and send self-messages. An alternative would be to have
|
|
|
|
|
different accounts that join a channel or message each other. Still needs
|
|
|
|
|
account configuration.
|
|
|
|
|
* irc could be used. With a default irc network, and an agreed-upon channel,
|
|
|
|
|
no configuration should be needed. IRC might be harder to get through
|
|
|
|
|
some firewalls, and is prone to netsplits, etc. IRC networks have reasons
|
|
|
|
|
to be wary of bots using them. Only basic notifications could be done over
|
|
|
|
|
irc, as it has little security.
|
|
|
|
|
* When there's a ssh server involved, code could be run on it to notify
|
|
|
|
|
logged-in clients. But this is not a general solution to this problem.
|
|
|
|
|
* pubsubhubbub does not seem like an option; its hubs want to pull down
|
|
|
|
|
a feed over http.
|
|
|
|
|
|
2012-05-29 23:17:38 +00:00
|
|
|
## storing git repos in the cloud
|
|
|
|
|
|
|
|
|
|
Of course, one option is to just use github etc to store the git repo.
|
|
|
|
|
|
2012-08-15 18:31:42 +00:00
|
|
|
Two things can store git repos in Amazon S3:
|
2012-05-29 23:17:38 +00:00
|
|
|
* <http://gabrito.com/post/storing-git-repositories-in-amazon-s3-for-high-availability>
|
|
|
|
|
* <http://wiki.cs.pdx.edu/oss2009/index/projects/gits3.html>
|
|
|
|
|
|
|
|
|
|
Another option is to not store the git repo in the cloud, but push/pull
|
|
|
|
|
peer-to-peer. When peers cannot directly talk to one-another, this could be
|
|
|
|
|
bounced through something like XMPP.
|
