emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Cooperating with oneself using the cloud?
Date: Mon, 15 Sep 2014 19:23:18 +0800	[thread overview]
Message-ID: <87sijtb00p.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CAHxk2pAg_=K=Dx-m1bmvDyu4tvA_dMPm6MJMWL28_+bZgXyDkA@mail.gmail.com

Martin Schöön <martin.schoon@gmail.com> writes:

> One of the things I use org-mode for is making and maintaining
> TODO-lists. I do this at home and at work and I want the org-files of
> interest to be available and up-to-date at home and at work. The
> work-related org-file can not be publicly available for obvious
> reasons.
>
> I have emailed these files back and forth. This works but it isn't
> fool-proof (sometimes I forget) and I think there should be a less
> clumsy way to do this.
>
> I have tried a  free and secure web-dav service. They are closing
> down and it also was a bit on the clumsy side since I never got their
> windows client to work at work. (Linux at home using cadaver.)
>
> I have seen Git being mentioned in this context in these nooks of the
> woods. That should work if I can find a free Git repository allowing
> me to keep files secret. I have looked at a few but have not seen
> (key word!) clear information on this.
>
> Options like BitTorrent Sync work really well but only if both
> computers run simultaneous which is not the case.
>
> Other options? Dropboxish services that keep prying eyes at bay?

At some point you might consider renting a little server space -- you
have to pay, but it's awfully useful for many things.

Another option would be getting a mini home server that sits in a closet
and is always on. That solves the BitTorrent Sync problem, and you'll
suddenly find it's good for a bunch of other stuff as well: backups,
music, printing, other torrents, LAN filesharing...

Both options are annoying in their own way, but once you've got
something up and running, you'll be pleased!

E

  parent reply	other threads:[~2014-09-15 11:19 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 [this message]
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
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=87sijtb00p.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).