From 7a10bc34f5fa6a085b1754f23420310d888244c6 Mon Sep 17 00:00:00 2001 From: "http://edheil.wordpress.com/" Date: Thu, 29 Nov 2012 22:15:12 +0000 Subject: [PATCH 01/21] Added a comment --- .../comment_7_615641b3dd176d4b3a5bbfb521098e38._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/forum/dot_git_slash_annex_slash_tmp/comment_7_615641b3dd176d4b3a5bbfb521098e38._comment diff --git a/doc/forum/dot_git_slash_annex_slash_tmp/comment_7_615641b3dd176d4b3a5bbfb521098e38._comment b/doc/forum/dot_git_slash_annex_slash_tmp/comment_7_615641b3dd176d4b3a5bbfb521098e38._comment new file mode 100644 index 0000000000..20e8b205f6 --- /dev/null +++ b/doc/forum/dot_git_slash_annex_slash_tmp/comment_7_615641b3dd176d4b3a5bbfb521098e38._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="http://edheil.wordpress.com/" + ip="173.162.44.162" + subject="comment 7" + date="2012-11-29T22:15:11Z" + content=""" +Sounds likely!! I'll get to deleting, and when I get a chance I'll grab your latest commit and recompile. + +"""]] From 4abd92e6cc921ab983613081373d60db196cdf7b Mon Sep 17 00:00:00 2001 From: "http://edheil.wordpress.com/" Date: Thu, 29 Nov 2012 22:15:55 +0000 Subject: [PATCH 02/21] Added a comment --- .../comment_8_4600fa9234a787004ea0e0dbb36184b9._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/dot_git_slash_annex_slash_tmp/comment_8_4600fa9234a787004ea0e0dbb36184b9._comment diff --git a/doc/forum/dot_git_slash_annex_slash_tmp/comment_8_4600fa9234a787004ea0e0dbb36184b9._comment b/doc/forum/dot_git_slash_annex_slash_tmp/comment_8_4600fa9234a787004ea0e0dbb36184b9._comment new file mode 100644 index 0000000000..3325f598a5 --- /dev/null +++ b/doc/forum/dot_git_slash_annex_slash_tmp/comment_8_4600fa9234a787004ea0e0dbb36184b9._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://edheil.wordpress.com/" + ip="173.162.44.162" + subject="comment 8" + date="2012-11-29T22:15:55Z" + content=""" +(thanks very much!) +"""]] From 24fdb40d3fb155fe06d8433ab4f83430b53d36c7 Mon Sep 17 00:00:00 2001 From: EskildHustvedt Date: Thu, 29 Nov 2012 22:39:15 +0000 Subject: [PATCH 03/21] --- ...rs_for_a_host_to_the_end_of_the_queue_when_one_fails.mdwn | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 doc/todo/wishlist:_move_pending_transfers_for_a_host_to_the_end_of_the_queue_when_one_fails.mdwn diff --git a/doc/todo/wishlist:_move_pending_transfers_for_a_host_to_the_end_of_the_queue_when_one_fails.mdwn b/doc/todo/wishlist:_move_pending_transfers_for_a_host_to_the_end_of_the_queue_when_one_fails.mdwn new file mode 100644 index 0000000000..966c59d95b --- /dev/null +++ b/doc/todo/wishlist:_move_pending_transfers_for_a_host_to_the_end_of_the_queue_when_one_fails.mdwn @@ -0,0 +1,5 @@ +Right now the assistant can have a huge list of pending transfers for certain hosts if its data is a bit outdated, or a host hasn't been synced lately. When starting up it will then attempt each transfer to said host (which will in turn fail, but at times take time to time out), possibly before doing other stuff like attempting to download new files, or copy files to online hosts. + +I suggest that if a transfer fails for host X, and there are other pending transfers, say to host Y and from Z, then all other pending transfers to/from X gets pushed to the back of the queue, to avoid having to wait a long time for several transfers to time out before doing useful stuff. + +The prime example for me was this morning, when a laptop that was turned off had a huge amount of queued transfers to it, resulting in the assistant attempting a load of transfers to that host before it retrieved a new file that I had created on another machine yesterday. From fc8ee478844abf6cb6d29684ddd59f38aaf45e5a Mon Sep 17 00:00:00 2001 From: Steve Date: Thu, 29 Nov 2012 23:51:21 +0000 Subject: [PATCH 04/21] Added a comment --- ...4_baa8fbbdd5c449a0dc2bb622cb4a47ce._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/forum/__34__du__34___equivalent_on_an_annex__63__/comment_4_baa8fbbdd5c449a0dc2bb622cb4a47ce._comment diff --git a/doc/forum/__34__du__34___equivalent_on_an_annex__63__/comment_4_baa8fbbdd5c449a0dc2bb622cb4a47ce._comment b/doc/forum/__34__du__34___equivalent_on_an_annex__63__/comment_4_baa8fbbdd5c449a0dc2bb622cb4a47ce._comment new file mode 100644 index 0000000000..227c74b026 --- /dev/null +++ b/doc/forum/__34__du__34___equivalent_on_an_annex__63__/comment_4_baa8fbbdd5c449a0dc2bb622cb4a47ce._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="Steve" + ip="92.104.175.136" + subject="comment 4" + date="2012-11-29T23:51:21Z" + content=""" +I've been thinking about writing a sort of git-annex du. I'm surprised to find someone else looking for such a thing. While \"du -L\" will tell you how much space is used by files you actually have, I was interested in knowing (approximately) how much space would be used if you were to git-annex get everything you don't yet have. + +There are many options and variations to think about, such as: + +* do you want to count duplicate files once or as many times as they appear (as if you 'git-annex lock'd them all) +* maybe you want to know how much space is used by files that reside only on a certain remote or set of remotes +* you might want to know how much space would be used by all the files you don't yet have, but not count the files you already have + +All of the backends so so far seem to store the size of the files in the filename, so my plan was to read it out of the links. If anybody has a better idea about how to get the sizes of annexed files or options that would be handy for a git-annex du, let me know. I'll see if I can get the start of something useful this weekend. I'll post here when I have something to share. + +I'm also open to suggestions for the executable name. Right now I'm thinking \"gadu\" for git-annex disk usage. +"""]] From bba8b4568774d583035895aa8ea611b246411eeb Mon Sep 17 00:00:00 2001 From: "http://sunny256.sunbase.org/" Date: Fri, 30 Nov 2012 00:29:45 +0000 Subject: [PATCH 05/21] Added a comment --- ...comment_5_2ee6cbbfe54a2e7b6e8eb539c18e663d._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/__34__du__34___equivalent_on_an_annex__63__/comment_5_2ee6cbbfe54a2e7b6e8eb539c18e663d._comment diff --git a/doc/forum/__34__du__34___equivalent_on_an_annex__63__/comment_5_2ee6cbbfe54a2e7b6e8eb539c18e663d._comment b/doc/forum/__34__du__34___equivalent_on_an_annex__63__/comment_5_2ee6cbbfe54a2e7b6e8eb539c18e663d._comment new file mode 100644 index 0000000000..021614405d --- /dev/null +++ b/doc/forum/__34__du__34___equivalent_on_an_annex__63__/comment_5_2ee6cbbfe54a2e7b6e8eb539c18e663d._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://sunny256.sunbase.org/" + nickname="sunny256" + subject="comment 5" + date="2012-11-30T00:29:44Z" + content=""" +Steve, that would be a very useful utility. I've been thinking of such a tool, but haven't gotten around to write it yet. It would be practical to have before copying big/many files from another drive. If I've been short of free space, I've executed `du -L` in the source directory, but that's a bit cumbersome. + +And \"gadu\" is a fine name, yes. Goes well along with my \"ga\" shortcut for \"git annex\", which I created two hours after I started using git-annex. I've probably saved thousands of keystrokes because of that. ☺ +"""]] From ca51fd4f7abbc046698b2bb895774db7855d62f1 Mon Sep 17 00:00:00 2001 From: "http://edheil.wordpress.com/" Date: Fri, 30 Nov 2012 05:32:27 +0000 Subject: [PATCH 06/21] --- doc/forum/git-assistant_clarification.mdwn | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/forum/git-assistant_clarification.mdwn diff --git a/doc/forum/git-assistant_clarification.mdwn b/doc/forum/git-assistant_clarification.mdwn new file mode 100644 index 0000000000..472f96c6a9 --- /dev/null +++ b/doc/forum/git-assistant_clarification.mdwn @@ -0,0 +1,11 @@ +I've noticed that if I'm using git-assistant, it wants to pull down all my files from other repos onto my laptop, even after I've dropped them. (My laptop is set up as "client," my usb drive and an ssh server as "backup".) + +I want to use git annex to save space on my laptop, but of course when I'm running the assistant, it pulls everything down there, even things I've manually dropped. + +Is my "I want to save space, with a partial archive on my laptop" use case simply out of scope for the assistant? So I should just be using the command line for my needs? That's fine if that's the case. + +Or maybe something like this is what I should be doing? http://git-annex.branchable.com/assistant/archival_walkthrough/ ? so instead of manually "git annex drop"-ping files in place, I should set up a directory called "archive" on my machine, from which files will magically disappear and get backed up elsewhere? + +If it's the case that a directory named "archive" in your checkout has the magical property of having the assistant drop and archive its contents, that's awesome, maybe just what I need, but if that behavior is spelled out in so many words anywhere I managed to miss it. + +Apologies for all these questions, just enjoying the software immensely and wanting to get to know it. From 0d5b9a20b57c626a26202a8d1e96429c23570f3f Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawn7gQ1zZDdWhXy9H51W2krZYShNmKL3qfM" Date: Fri, 30 Nov 2012 08:26:25 +0000 Subject: [PATCH 07/21] Added a comment --- ...ent_1_8f553e59da12f798b854a457b96b5778._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/forum/git-assistant_clarification/comment_1_8f553e59da12f798b854a457b96b5778._comment diff --git a/doc/forum/git-assistant_clarification/comment_1_8f553e59da12f798b854a457b96b5778._comment b/doc/forum/git-assistant_clarification/comment_1_8f553e59da12f798b854a457b96b5778._comment new file mode 100644 index 0000000000..03f9dc2735 --- /dev/null +++ b/doc/forum/git-assistant_clarification/comment_1_8f553e59da12f798b854a457b96b5778._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawn7gQ1zZDdWhXy9H51W2krZYShNmKL3qfM" + nickname="Karsten" + subject="comment 1" + date="2012-11-30T08:26:24Z" + content=""" +I'm second this request. Also, I'm posting this to enable the rss comment subscription button for this post. + +Maybe these design documents are interesting: + + + + +"""]] From cee80ef4c7ecb45b012051ad760c16d91671b3b6 Mon Sep 17 00:00:00 2001 From: "98.165.29.103" <98.165.29.103@web> Date: Fri, 30 Nov 2012 09:58:55 +0000 Subject: [PATCH 08/21] poll vote (Tahoe-LAFS) --- doc/design/assistant/polls/prioritizing_special_remotes.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/design/assistant/polls/prioritizing_special_remotes.mdwn b/doc/design/assistant/polls/prioritizing_special_remotes.mdwn index 93c4b37d94..fa8d599bda 100644 --- a/doc/design/assistant/polls/prioritizing_special_remotes.mdwn +++ b/doc/design/assistant/polls/prioritizing_special_remotes.mdwn @@ -6,7 +6,7 @@ locally paired systems, and remote servers with rsync. Help me prioritize my work: What special remote would you most like to use with the git-annex assistant? -[[!poll open=yes 15 "Amazon S3 (done)" 12 "Amazon Glacier (done)" 9 "Box.com (done)" 63 "My phone (or MP3 player)" 16 "Tahoe-LAFS" 6 "OpenStack SWIFT" 23 "Google Drive"]] +[[!poll open=yes 15 "Amazon S3 (done)" 12 "Amazon Glacier (done)" 9 "Box.com (done)" 63 "My phone (or MP3 player)" 17 "Tahoe-LAFS" 6 "OpenStack SWIFT" 23 "Google Drive"]] This poll is ordered with the options I consider easiest to build listed first. Mostly because git-annex already supports them and they From 628a314b1a3abe669bc5f5fbb7881d318910a169 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" Date: Fri, 30 Nov 2012 14:38:42 +0000 Subject: [PATCH 09/21] Use case for two-way sync using your own metal --- ...tralized_repository_behind_a_Firewall.mdwn | 52 +++++++++++++++++++ 1 file changed, 52 insertions(+) create mode 100644 doc/tips/Decentralized_repository_behind_a_Firewall.mdwn diff --git a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn new file mode 100644 index 0000000000..c43defe1a0 --- /dev/null +++ b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn @@ -0,0 +1,52 @@ +If you're anything like me, you have a copy of your annex on a computer running at home¹, set up so you can access it from anywhere like this: + + ssh myhome.no-ip.org + +This is totally great! Except, there is no way for your home computer to pull your changes, because there is no onthego.no-ip.org. You can get clunky and use a bare git repository and git push, but there is a better way. + +First, install openssh-server on your on-the-go computer + + sudo apt-get install openssh-server + +Then, log into your home computer, with *port forwarding*: + + ssh me@myhome.no-ip.org L 2201:localhost:22 + +Your home computer can now ssh into your on-the-go computer, as long as you keep the above shell running. Presto, you can use the same shell to set up your remote: + + ssh-keygen -t rsa + ssh-copy-id localhost -p 2201 + cd ~/annex + git annex remote add on-the-go ssh://localhost:2201/home/myuser/annex + +And run normal annex operations: + + git annex sync + git annex get on-the-go some/big/file + git annex status + +You can add more computers by repeating with a different port, e.g. 2202 or 2203 (or any other). + +If you're security paranoid (like me), read on. If you're not, that's it! Thanks for reading! + +--- paranoid area --- + +Note you're granting passwordless access to your on-the-go computer to your home computer. I believe that's all right, as long as: + +* Your home computer is really in your home, and not at a friend's house or some datacenter +* Your home computer can be accessed only by ssh, and not HTTP or Samba or NTP or (shoot me now!) FTP +* Only you (and perhaps trustworthy family) have access to your home computer +* You have reasonably strong passwords or key-only logins on both your home and on-the-go computers. +* You regularly install security updates on both computers (sudo apt-get update && sudo apt-get upgrade) + +In any case, the setup is much, much, much more secure than Dropbox. With Dropbox, you have exactly the same setup, but: + +* Your data is stored in some datacenter. It's supposed to be encrypted. It might not be. +* Lot's of people have routine access to your files, and plausible reason to. Bored employees might regularly be doing some 'maintenance work' involving your pictures. +* The dropbox software can do anything it likes on your computer, and it's closed source and can't be audited +* Any dropbox employee can conveiably use your installed dropbox to look at any file on your computer +* A truly huge amount of eyes connected to incredibly smart brains have looked at openssh and found it secure. Everybody trusts openssh. With dropbox, there is, well, dropbox. Whoever that is. + +----- + +¹ My always-on computer at home is a raspberry pi with a 32GB USB stick. Best self-hosted dropbox you could imagine. From 3430f978cbe0202287e06f3c33cfe207c430614b Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" Date: Fri, 30 Nov 2012 14:41:15 +0000 Subject: [PATCH 10/21] --- ...tralized_repository_behind_a_Firewall.mdwn | 25 +++++++++---------- 1 file changed, 12 insertions(+), 13 deletions(-) diff --git a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn index c43defe1a0..8527b1a0f3 100644 --- a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn +++ b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn @@ -1,36 +1,36 @@ If you're anything like me, you have a copy of your annex on a computer running at home¹, set up so you can access it from anywhere like this: - ssh myhome.no-ip.org + ssh myhome.no-ip.org This is totally great! Except, there is no way for your home computer to pull your changes, because there is no onthego.no-ip.org. You can get clunky and use a bare git repository and git push, but there is a better way. First, install openssh-server on your on-the-go computer - sudo apt-get install openssh-server + sudo apt-get install openssh-server Then, log into your home computer, with *port forwarding*: - ssh me@myhome.no-ip.org L 2201:localhost:22 + ssh me@myhome.no-ip.org L 2201:localhost:22 Your home computer can now ssh into your on-the-go computer, as long as you keep the above shell running. Presto, you can use the same shell to set up your remote: - ssh-keygen -t rsa - ssh-copy-id localhost -p 2201 - cd ~/annex - git annex remote add on-the-go ssh://localhost:2201/home/myuser/annex + ssh-keygen -t rsa + ssh-copy-id localhost -p 2201 + cd ~/annex + git annex remote add on-the-go ssh://localhost:2201/home/myuser/annex And run normal annex operations: - git annex sync - git annex get on-the-go some/big/file - git annex status + git annex sync + git annex get on-the-go some/big/file + git annex status You can add more computers by repeating with a different port, e.g. 2202 or 2203 (or any other). If you're security paranoid (like me), read on. If you're not, that's it! Thanks for reading! ---- paranoid area --- - +Paranoid Area +--- Note you're granting passwordless access to your on-the-go computer to your home computer. I believe that's all right, as long as: * Your home computer is really in your home, and not at a friend's house or some datacenter @@ -46,7 +46,6 @@ In any case, the setup is much, much, much more secure than Dropbox. With Dropbo * The dropbox software can do anything it likes on your computer, and it's closed source and can't be audited * Any dropbox employee can conveiably use your installed dropbox to look at any file on your computer * A truly huge amount of eyes connected to incredibly smart brains have looked at openssh and found it secure. Everybody trusts openssh. With dropbox, there is, well, dropbox. Whoever that is. - ----- ¹ My always-on computer at home is a raspberry pi with a 32GB USB stick. Best self-hosted dropbox you could imagine. From a22fd46bcc01c569c8ae9c3c52b4255fde2badc9 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" Date: Fri, 30 Nov 2012 14:41:58 +0000 Subject: [PATCH 11/21] --- doc/tips/Decentralized_repository_behind_a_Firewall.mdwn | 1 + 1 file changed, 1 insertion(+) diff --git a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn index 8527b1a0f3..e720522a4b 100644 --- a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn +++ b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn @@ -30,6 +30,7 @@ You can add more computers by repeating with a different port, e.g. 2202 or 2203 If you're security paranoid (like me), read on. If you're not, that's it! Thanks for reading! Paranoid Area + --- Note you're granting passwordless access to your on-the-go computer to your home computer. I believe that's all right, as long as: From 07c2a6a33a7e1faf8bbe3a6b62e3ef8e89d10d31 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" Date: Fri, 30 Nov 2012 14:49:02 +0000 Subject: [PATCH 12/21] --- .../Decentralized_repository_behind_a_Firewall.mdwn | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn index e720522a4b..c2a1147996 100644 --- a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn +++ b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn @@ -2,24 +2,26 @@ If you're anything like me, you have a copy of your annex on a computer running ssh myhome.no-ip.org -This is totally great! Except, there is no way for your home computer to pull your changes, because there is no onthego.no-ip.org. You can get clunky and use a bare git repository and git push, but there is a better way. +This is totally great! Except, there is no way for your home computer to pull your changes, because there is no *on-the-go.no-ip.org*. You can get clunky and use a *bare git repository and git push*, but there is a better way. -First, install openssh-server on your on-the-go computer +First, install *openssh-server* on your *on-the-go* computer sudo apt-get install openssh-server -Then, log into your home computer, with *port forwarding*: +Then, log into your *home* computer, with *port forwarding*: ssh me@myhome.no-ip.org L 2201:localhost:22 -Your home computer can now ssh into your on-the-go computer, as long as you keep the above shell running. Presto, you can use the same shell to set up your remote: +Your *home* computer can now ssh into your *on-the-go* computer, as long as you keep the above shell running. + +You can now add your *on-the-go* computer as a remote on your *home* computer. Use the port forwarding shell you just connected with the command above, if you like. ssh-keygen -t rsa ssh-copy-id localhost -p 2201 cd ~/annex git annex remote add on-the-go ssh://localhost:2201/home/myuser/annex -And run normal annex operations: +Now you can run normal annex operations, as long as the port forwarding shell is running². git annex sync git annex get on-the-go some/big/file @@ -50,3 +52,4 @@ In any case, the setup is much, much, much more secure than Dropbox. With Dropbo ----- ¹ My always-on computer at home is a raspberry pi with a 32GB USB stick. Best self-hosted dropbox you could imagine. +² You can just forward the port, but not open a shell, by adding the -N command. I rarely use this. From e161583606804abae96467efa813838621632073 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" Date: Fri, 30 Nov 2012 14:49:53 +0000 Subject: [PATCH 13/21] --- doc/tips/Decentralized_repository_behind_a_Firewall.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn index c2a1147996..ff2b1706a5 100644 --- a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn +++ b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn @@ -6,7 +6,7 @@ This is totally great! Except, there is no way for your home computer to pull yo First, install *openssh-server* on your *on-the-go* computer - sudo apt-get install openssh-server + sudo apt-get install openssh-serverpa Then, log into your *home* computer, with *port forwarding*: @@ -31,9 +31,9 @@ You can add more computers by repeating with a different port, e.g. 2202 or 2203 If you're security paranoid (like me), read on. If you're not, that's it! Thanks for reading! +--- Paranoid Area ---- Note you're granting passwordless access to your on-the-go computer to your home computer. I believe that's all right, as long as: * Your home computer is really in your home, and not at a friend's house or some datacenter From d14c3def2b5233e507f3041b5bce97678d9a3381 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" Date: Fri, 30 Nov 2012 14:51:35 +0000 Subject: [PATCH 14/21] --- doc/tips/Decentralized_repository_behind_a_Firewall.mdwn | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn index ff2b1706a5..471a08c58e 100644 --- a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn +++ b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn @@ -52,4 +52,5 @@ In any case, the setup is much, much, much more secure than Dropbox. With Dropbo ----- ¹ My always-on computer at home is a raspberry pi with a 32GB USB stick. Best self-hosted dropbox you could imagine. -² You can just forward the port, but not open a shell, by adding the -N command. I rarely use this. + +² You can just forward the port, but not open a shell, by adding the -N command. This could be useful for connecting on startup, e.g. in /etc/rc.local. I prefer to open the shell to forward the ports, maybe use it, and close it to stop it. From 36c86adc95588b2a2547a12b090674f4a5cada08 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" Date: Fri, 30 Nov 2012 14:54:10 +0000 Subject: [PATCH 15/21] --- .../Decentralized_repository_behind_a_Firewall.mdwn | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn index 471a08c58e..43c8a50063 100644 --- a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn +++ b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn @@ -1,4 +1,4 @@ -If you're anything like me, you have a copy of your annex on a computer running at home¹, set up so you can access it from anywhere like this: +If you're anything like me¹, you have a copy of your annex on a computer running at home², set up so you can access it from anywhere like this: ssh myhome.no-ip.org @@ -21,7 +21,7 @@ You can now add your *on-the-go* computer as a remote on your *home* computer. U cd ~/annex git annex remote add on-the-go ssh://localhost:2201/home/myuser/annex -Now you can run normal annex operations, as long as the port forwarding shell is running². +Now you can run normal annex operations, as long as the port forwarding shell is running³. git annex sync git annex get on-the-go some/big/file @@ -51,6 +51,8 @@ In any case, the setup is much, much, much more secure than Dropbox. With Dropbo * A truly huge amount of eyes connected to incredibly smart brains have looked at openssh and found it secure. Everybody trusts openssh. With dropbox, there is, well, dropbox. Whoever that is. ----- -¹ My always-on computer at home is a raspberry pi with a 32GB USB stick. Best self-hosted dropbox you could imagine. +¹ Me=Carlo, not Joey. Just noting so this you can direct potential flames at the correct person. -² You can just forward the port, but not open a shell, by adding the -N command. This could be useful for connecting on startup, e.g. in /etc/rc.local. I prefer to open the shell to forward the ports, maybe use it, and close it to stop it. +² My always-on computer at home is a raspberry pi with a 32GB USB stick. Best self-hosted dropbox you could imagine. + +³ You can just forward the port, but not open a shell, by adding the -N command. This could be useful for connecting on startup, e.g. in /etc/rc.local. I prefer to open the shell to forward the ports, maybe use it, and close it to stop it. From 6d4ce7df9dbf1ce5891a31e49e53d37f10245b89 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" Date: Fri, 30 Nov 2012 14:55:40 +0000 Subject: [PATCH 16/21] --- doc/tips/Decentralized_repository_behind_a_Firewall.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn index 43c8a50063..61bc89c09f 100644 --- a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn +++ b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn @@ -51,7 +51,7 @@ In any case, the setup is much, much, much more secure than Dropbox. With Dropbo * A truly huge amount of eyes connected to incredibly smart brains have looked at openssh and found it secure. Everybody trusts openssh. With dropbox, there is, well, dropbox. Whoever that is. ----- -¹ Me=Carlo, not Joey. Just noting so this you can direct potential flames at the correct person. +¹ Me=Carlo, not Joey. I'm pretty sure doing what I wrote here is a good idea, but in case it turns out to be catastrophically dumb, it's my fault, not his. ² My always-on computer at home is a raspberry pi with a 32GB USB stick. Best self-hosted dropbox you could imagine. From f2d4fe9186ba00ba9bca2e178096b8a47f4002a9 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" Date: Fri, 30 Nov 2012 14:57:25 +0000 Subject: [PATCH 17/21] --- doc/tips/Decentralized_repository_behind_a_Firewall.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn index 61bc89c09f..5b066c22d8 100644 --- a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn +++ b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn @@ -6,7 +6,7 @@ This is totally great! Except, there is no way for your home computer to pull yo First, install *openssh-server* on your *on-the-go* computer - sudo apt-get install openssh-serverpa + sudo apt-get install openssh-server # Adjust to your flavor of unix Then, log into your *home* computer, with *port forwarding*: From 8ef48757218a1b80d9e7f48a176161209d9ac877 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" Date: Fri, 30 Nov 2012 15:02:16 +0000 Subject: [PATCH 18/21] --- doc/tips/Decentralized_repository_behind_a_Firewall.mdwn | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn index 5b066c22d8..9fea58527e 100644 --- a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn +++ b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn @@ -46,9 +46,10 @@ In any case, the setup is much, much, much more secure than Dropbox. With Dropbo * Your data is stored in some datacenter. It's supposed to be encrypted. It might not be. * Lot's of people have routine access to your files, and plausible reason to. Bored employees might regularly be doing some 'maintenance work' involving your pictures. -* The dropbox software can do anything it likes on your computer, and it's closed source and can't be audited -* Any dropbox employee can conveiably use your installed dropbox to look at any file on your computer +* The dropbox software can do anything it likes on your computer, and it's closed source so you don't know if it does. A disgruntled employee could put a trojan into it. +* Dropbox might have a backdoor for employee access to any file on your computer. This might be done with the best of intentions, but a mal-intentioned or careless employee might still erase things or send sensitive files from your computer by email. * A truly huge amount of eyes connected to incredibly smart brains have looked at openssh and found it secure. Everybody trusts openssh. With dropbox, there is, well, dropbox. Whoever that is. + ----- ¹ Me=Carlo, not Joey. I'm pretty sure doing what I wrote here is a good idea, but in case it turns out to be catastrophically dumb, it's my fault, not his. From f0b6f71cfe7f3840dadb1442f3cc384fad0b0c72 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" Date: Fri, 30 Nov 2012 15:03:56 +0000 Subject: [PATCH 19/21] --- doc/tips/Decentralized_repository_behind_a_Firewall.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn index 9fea58527e..5dbc8d71a3 100644 --- a/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn +++ b/doc/tips/Decentralized_repository_behind_a_Firewall.mdwn @@ -17,9 +17,9 @@ Your *home* computer can now ssh into your *on-the-go* computer, as long as you You can now add your *on-the-go* computer as a remote on your *home* computer. Use the port forwarding shell you just connected with the command above, if you like. ssh-keygen -t rsa - ssh-copy-id localhost -p 2201 + ssh-copy-id me@localhost -p 2201 cd ~/annex - git annex remote add on-the-go ssh://localhost:2201/home/myuser/annex + git annex remote add on-the-go ssh://me@localhost:2201/home/myuser/annex Now you can run normal annex operations, as long as the port forwarding shell is running³. From d0e35b87ef39b9720e523bff1d395b6bef43ea33 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 30 Nov 2012 16:26:01 +0000 Subject: [PATCH 20/21] Added a comment --- .../comment_1_78b9035234a690ca5a7c9f3cc78fa092._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/tips/Decentralized_repository_behind_a_Firewall/comment_1_78b9035234a690ca5a7c9f3cc78fa092._comment diff --git a/doc/tips/Decentralized_repository_behind_a_Firewall/comment_1_78b9035234a690ca5a7c9f3cc78fa092._comment b/doc/tips/Decentralized_repository_behind_a_Firewall/comment_1_78b9035234a690ca5a7c9f3cc78fa092._comment new file mode 100644 index 0000000000..71a1db9c88 --- /dev/null +++ b/doc/tips/Decentralized_repository_behind_a_Firewall/comment_1_78b9035234a690ca5a7c9f3cc78fa092._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.6.49" + subject="comment 1" + date="2012-11-30T16:25:58Z" + content=""" +If you don't trust your home computer with shell access, you can lock it down in `.ssh/authorized_keys` to only be able to run git-annex-shell. See [[forum/Restricting_git-annex-shell_to_a_specific_repository]] +"""]] From b9e0e661cd51747bf23d9c1774d697c38ce589f7 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 30 Nov 2012 16:31:21 +0000 Subject: [PATCH 21/21] Added a comment --- ...comment_2_06cf62b599edea6ad8396776f0081494._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/git-assistant_clarification/comment_2_06cf62b599edea6ad8396776f0081494._comment diff --git a/doc/forum/git-assistant_clarification/comment_2_06cf62b599edea6ad8396776f0081494._comment b/doc/forum/git-assistant_clarification/comment_2_06cf62b599edea6ad8396776f0081494._comment new file mode 100644 index 0000000000..90137e722f --- /dev/null +++ b/doc/forum/git-assistant_clarification/comment_2_06cf62b599edea6ad8396776f0081494._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.6.49" + subject="comment 2" + date="2012-11-30T16:31:21Z" + content=""" +The archive directory is a new feature, but yes, it does work. Just use the webapp to edit the configuration of a remote, put it into the \"small archive\" group, and the contents of archive directories will be sent to it. + +This is a particular application of [[preferred_content]] settings, which give you a large amount of control over which data end up where when using the assistant. +"""]]