emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: rey-coyrehourcq <sebastien.rey-coyrehourcq@univ-rouen.fr>
To: emacs-orgmode@gnu.org
Subject: How to replace secrets during org-babel tangle/export without loosing the reproductibility of original script ?
Date: Thu, 10 Sep 2020 21:55:28 +0200	[thread overview]
Message-ID: <78ce8771b0de8a51d69a8ad87d63c8288546c929.camel@univ-rouen.fr> (raw)

Hi there, 

First thanks again guys for all the works you doing on org-mode !

I'm searching a way or an example of workflow for such a thing i consider as a common pattern for reproductibility
(reproductible papers in science for example).

For example, i'm starting writing a blog post with org-mode and org-babel to deploy, for example, a nixOS system on a
VPS. I wrote some bash scripts and a configuration.nix for nixOS which contains my gpg key, my vps password, and so
on... When everything works right, i'm ready to publish my full working tutorial on web.

BUT as you imagine, i don't want to share secrets/password ... 

- A first solution was to replace password by some "foo-bar" things, but doing that i lost all the reproductibility of
this script in the future ... so this is silly.

- A second solution, i suppose, was to dynamically choose if i want to replace or not password/secrets/etc by "foo-bar"
things during tangle/export of the script. 

Because i'm not an expert in org-babel headers (so much possibilities ...), if you have some ready to go template/script
to do that into org-babel, i'm interested !

Best !


Sébastien Rey-Coyrehourcq
Research Engineer UMR IDEES

{Stronger security for your email, follow EFF tutorial : https://ssd.eff.org/}

                 reply	other threads:[~2020-09-10 19:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

  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=78ce8771b0de8a51d69a8ad87d63c8288546c929.camel@univ-rouen.fr \
    --to=sebastien.rey-coyrehourcq@univ-rouen.fr \
    --cc=emacs-orgmode@gnu.org \


* 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


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).