emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Samuel Banya" <sbanya@fastmail.com>
To: "Juan Manuel Macías" <maciaschain@posteo.net>
Cc: Charles Berry <emacs-orgmode@gnu.org>
Subject: Re: literate programming, development log -- ideas? (ominbus reply)
Date: Fri, 11 Jun 2021 11:02:04 -0400	[thread overview]
Message-ID: <b72d3c82-51e2-4569-af68-b2d31d734b9d@www.fastmail.com> (raw)
In-Reply-To: <87a6nwcw2s.fsf@posteo.net>

[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]

Now this idea I like!

Thanks for this, I didn't think about using the Git repo as a SECONDARY backup source.

Also, using Nextcloud sounds like a neat idea.

I'm into Self-Hosting stuff myself nowadays but am starting out small (ex: Just bought an old Dell Optiplex from eBay, put 2 HDDs into it, planning on using it for HDD backups, and as a Git server).

However, this sounds like an awesome workflow, as I did not consider to host Nextcloud. Awesome idea, thank you for this, Juan!

On Fri, Jun 11, 2021, at 10:30 AM, Juan Manuel Macías wrote:
> Samuel Banya writes:
> 
> > I'm okay with git repos for dot files or some kind of programming
> > project but yeah, I've been debating something else for an org based
> > repo cause I too have almost had my 'life.org' be completely destroyed
> > with a merge event.
> 
> I have all my everyday Org documents in a Nextcloud folder, but only
> because I work between the desktop PC and the laptop. I sync using a
> script with nextcloud-cmd, not via the Nextcloud app, which I find it
> somewhat intrusive. And with another script I do every week a backup of
> that folder to a git repo. But this repo is secondary and is only for
> keep some backups (I also keep a weekly backup of Elpa folders ---last
> versions--- there, in case some update breaks something).
> 
> Best regards,
> 
> Juan Manuel 
> 
> 
> 
> 

[-- Attachment #2: Type: text/html, Size: 2003 bytes --]

  reply	other threads:[~2021-06-11 15:03 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 11:43 literate programming, development log -- ideas? Greg Minshall
2021-06-07 12:00 ` Juan Manuel Macías
2021-06-08 17:15   ` literate programming, development log -- ideas? (ominbus reply) Greg Minshall
2021-06-08 17:21     ` Samuel Banya
2021-06-09  8:59       ` Eric S Fraga
2021-06-09 22:21         ` Dr. Arne Babenhauserheide
2021-06-10 22:07           ` Samuel Wales
2021-06-11  0:13             ` Samuel Banya
2021-06-11 14:30               ` Juan Manuel Macías
2021-06-11 15:02                 ` Samuel Banya [this message]
2021-06-09 14:52       ` Maxim Nikulin
2021-06-10 13:28         ` Greg Minshall
2021-06-11 19:51       ` Christian Barthel
2021-06-13  0:46       ` Tim Cross
2021-06-13 15:48         ` Samuel Banya
2021-06-13 23:13           ` Tim Cross
2021-06-09  8:57     ` Eric S Fraga
2021-06-13  0:31       ` Tim Cross
2021-06-13  4:27         ` Greg Minshall
2021-06-13  7:29           ` Tim Cross
2021-06-14  6:14             ` Greg Minshall
2021-06-07 12:08 ` literate programming, development log -- ideas? Eric S Fraga
2021-06-13  0:24   ` Tim Cross
2021-06-13 15:44     ` Samuel Banya
2021-06-14 12:57       ` Greg Minshall
2021-06-07 13:53 ` Dr. Arne Babenhauserheide
2021-06-07 17:59   ` briangpowell
2021-06-07 23:17     ` Dr. Arne Babenhauserheide
2021-06-08  2:06       ` Samuel Banya
2021-06-08  3:23         ` Greg Minshall
2021-06-08  3:31           ` Samuel Banya
2021-06-08  6:15             ` Greg Minshall
2021-06-08 16:59     ` Greg Minshall
2021-06-07 19:19 ` Jack Kamm

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=b72d3c82-51e2-4569-af68-b2d31d734b9d@www.fastmail.com \
    --to=sbanya@fastmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=maciaschain@posteo.net \
    /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).