summaryrefslogtreecommitdiff
path: root/doc/design/assistant/cloud.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-05-28 14:41:23 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-05-28 14:41:23 -0400
commita5da677b9e37747dfb86eda998ce92bd5ff80d03 (patch)
treeda74c20190dd112303e5b32c445e55ca60c1f107 /doc/design/assistant/cloud.mdwn
parent5d178d2aca257347fa0d402a933a45a350bd8ad5 (diff)
update
Diffstat (limited to 'doc/design/assistant/cloud.mdwn')
-rw-r--r--doc/design/assistant/cloud.mdwn28
1 files changed, 28 insertions, 0 deletions
diff --git a/doc/design/assistant/cloud.mdwn b/doc/design/assistant/cloud.mdwn
new file mode 100644
index 000000000..1d612feac
--- /dev/null
+++ b/doc/design/assistant/cloud.mdwn
@@ -0,0 +1,28 @@
+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
+
+Git-annex already supports several cloud providers via [[special_remotes].
+More should be added, such as:
+
+* Google drive (attractive because it's free)
+* OpenStack Swift
+* Box.com (it's free, and current method is hard to set up and a sorta
+ shakey)
+* Dropbox? That would be ironic..
+
+## limited space
+
+When syncing via the cloud, space there is probably limited, so
+users with more files than cloud space will want to be able to use the
+cloud as a temporary transfer point, which files are removed from after
+they've propigated out.
+
+Other users will want to use the cloud as the canonical or backup location
+of their data, and would want a copy of all their files to be kept there.
+That's also ok.
+
+git-annex will need a way to tell the difference between these, either
+heuristically, or via configuration.