unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: takev <takev@disroot.org>
To: Felix Lechner <felix.lechner@lease-up.com>,
	Felix Lechner via <help-guix@gnu.org>,
	Nathan Dehnel <ncdehnel@gmail.com>,
	help-guix@gnu.org
Subject: Re: What is the difference between the directories in / and in /run/current-system/profile?
Date: Fri, 21 Jun 2024 12:53:17 -0400	[thread overview]
Message-ID: <DBB2C3CE-C30B-449A-995C-1669DFFD29FA@disroot.org> (raw)
In-Reply-To: <875xw0161o.fsf@lease-up.com>

Just chiming in about the secrets, but I have found that guix-sops works really well so far: https://fishinthecalculator.me/blog/secrets-management-with-sops-guix.html

There are a few things I would like to see (i.e. symmetrical encryption, being able to use s-expressions instead of yaml, etc), but for the most part it works very well on my servers.


On April 29, 2024 12:34:43 PM EDT, Felix Lechner via <help-guix@gnu.org> wrote:

>Ideally, / would be empty, except for /gnu/store and mount points for
>/home and /root.  Some folks run / on a tmpfs and manage to get pretty
>close.  One challenge is that we haven't figured out what to do with
>secrets.  The store is public, so they can't go there.


      parent reply	other threads:[~2024-06-21 16:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-27 22:41 What is the difference between the directories in / and in /run/current-system/profile? Nathan Dehnel
2024-04-29 16:34 ` Felix Lechner via
2024-04-29 18:31   ` Nathan Dehnel
2024-06-21 16:53   ` takev [this message]

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DBB2C3CE-C30B-449A-995C-1669DFFD29FA@disroot.org \
    --to=takev@disroot.org \
    --cc=felix.lechner@lease-up.com \
    --cc=help-guix@gnu.org \
    --cc=ncdehnel@gmail.com \
    /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.
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).