From: "Monroe, Will" <wtmonroe.ls@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Cooperating with oneself using the cloud?
Date: Fri, 26 Sep 2014 13:58:31 -0500 [thread overview]
Message-ID: <5425B757.8060209@gmail.com> (raw)
In-Reply-To: <87lhp6v5dp.fsf@gmx.us>
Thanks you Rasmus and Brett! It still sounds interesting although your
combined feedback has left me in a state of indecision about whether to
pursue another option or investigate git-annex further. Ha!
On 9/26/14, 9:11 AM, Rasmus wrote:
> Hi,
>
> "Tim O'Callaghan" <timo@linux.com> writes:
>
>> I have no instructions per-se. I did consider git, using git-annexe or
>> similar tool, but the pre-internet encryption i require does not
>> easily happen out of the box. If you are only syncing between your own
>> git servers though and do not care so much file level encryption
>> git-annexe a remarkable tool. I still cannot get my head around how it
>> works (symlinks galore!) but it seems ideal for personal sync (but not
>> to github). This is the nearest thing i've seen to dropbox.
>> https://git-annex.branchable.com/
>
> At this point I would not recommend git-annex to my worst enemy, even
> though I use it. Annex is not at all transparent (to me), and I
> struggle a lot when it doesn't just worksᵀᴹ [which is somehow rarely
> the case for me].
>
> That being said, it does do client-side encryption. It will even
> setup a key for you in the webapp. Only requirement is that you have
> git-annex on your central server, but I think an installation by an
> unprivileged user is fine. You have to transfer the key to your other
> systems yourself.
>
> Also, you can get rid of the symlinks with direct mode. I sometimes
> go into indirect mode to do $GIT_STUFF manually.
>
> —Rasmus
>
next prev parent reply other threads:[~2014-09-26 18:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 10:59 Cooperating with oneself using the cloud? Martin Schöön
2014-09-15 11:06 ` Phil Mason
2014-09-24 16:29 ` Monroe, Will
2014-09-15 11:23 ` Eric Abrahamsen
2014-09-16 7:23 ` Eric S Fraga
2014-09-15 14:51 ` Bruno Bigras
2014-09-16 8:43 ` Ramon Diaz-Uriarte
2014-09-16 19:47 ` Martin Schöön
2014-09-15 19:30 ` Thierry Banel
2014-09-22 8:05 ` Christoph Groth
2014-09-24 15:07 ` Tim O'Callaghan
[not found] ` <87ppel6n4s.fsf@grothesque.org>
[not found] ` <CAArV04Nb0P4xGZP7SVg+OTV40xcrWScr9T23-H0=5VeciYo+Zw@mail.gmail.com>
2014-09-25 12:10 ` Fwd: " Tim O'Callaghan
2014-09-25 13:50 ` Monroe, Will
2014-09-25 14:17 ` Brett Viren
2014-09-26 14:11 ` Rasmus
2014-09-26 18:58 ` Monroe, Will [this message]
2014-10-29 20:13 ` Karl Voit
2014-10-30 8:09 ` Paul Rudin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5425B757.8060209@gmail.com \
--to=wtmonroe.ls@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).