unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "Daniel Meißner" <daniel.meissner-i4k@ruhr-uni-bochum.de>
Cc: "Sébastien Rey-Coyrehourcq"
	<sebastien.rey-coyrehourcq@univ-rouen.fr>,
	"Julien Lepiller" <julien@lepiller.eu>,
	help-guix@gnu.org
Subject: Re: Guix home, guix system, channels, some noob questions
Date: Wed, 25 May 2022 21:45:54 +0300	[thread overview]
Message-ID: <Yo55YnAKxhzWQF28@3900XT> (raw)
In-Reply-To: <87ee0hhh19.fsf@ruhr-uni-bochum.de>

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

On Wed, May 25, 2022 at 03:34:58PM +0200, Daniel Meißner wrote:
> Hi Sébastien,
> 
> Sébastien Rey-Coyrehourcq writes:
> 
> > Thanks,  in fact when i see *guix home* that was my first intention
> > (like home-manager in nix).
> >
> > The only things holding me back at the moment is two things :
> >
> > a) doom emacs flavour, how to manage the fact that doom use straigt.el
> > to maintain packages
> 
> I am sorry, I am not using Doom Emacs, so I cannot be of any help in
> this regard.  I manage my (relatively few) Emacs packages with Guix
> directly.
> 
> > b) "password / secrets" management ?
> >
> > There are two things, file to directly encrypt (like ssh key) and
> > password to hide into configuration file (templating)
> >
> > b.1) So, that need to encrypt/decrypt more or less "on-the-fly" the
> > files using gpg/yubikey or age like yadm (
> > https://yadm.io/docs/encryption ) or chezmoi
> > (https://www.chezmoi.io/user-guide/encryption/gpg/) do ?
> >
> > b.2) And for templating, like replacing ${mypassword} into some
> > configuration file by getting info stored into password manager like
> > "pass", i also don't know how to do that.
> >
> > Actually I have no idea how to do that with guile / guix home for b.1
> > / b.2
> 
> Yes, that's indeed a problem and I haven't come up with a solution.  I
> simply copy the respective files from machine to machine.  Maybe someone
> else on this list has a better idea...
> 
> > c) synchronization of my .dotfiles between two different OS/System :
> > Ubuntu (home) / Guix (work & home)
> >
> > Lot of people use Ubuntu in my work environment, so i need to maintain
> > some sort of compatibility between both systems for my dotfile (before
> > everyone use guix in 2030 ? :D).
> >
> > I suppose guix home work well with guix on top of ubuntu ?
> 
> Yes, I think so, I haven't tested it though.  You can, in principle,
> adapt the generated dotfiles to the machines you're deploying them to.
> You could, for example, use the hostname to distinguish them (untested):
> 
> --8<---------------cut here---------------start------------->8---
> (mixed-text-file
>  "test.txt"
>  "setting = "
>  #~(case (gethostname)
>      (("hosta") => "foo")
>      (("hostb") => "bar")
>      (else => "foobar")))
> --8<---------------cut here---------------end--------------->8---
> 

I check for /run/current-system/provenance¹ and based on that I make
some changes to what gets placed in my dot-files.

¹ https://git.sr.ht/~efraim/guix-config/tree/master/item/efraim-home.scm#L31
² https://git.sr.ht/~efraim/guix-config/tree/master/item/efraim-home.scm#L342-346

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-05-25 18:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  9:09 Guix home, guix system, channels, some noob questions Sébastien Rey-Coyrehourcq
2022-05-11 10:47 ` Julien Lepiller
2022-05-11 14:36   ` Sébastien Rey-Coyrehourcq
2022-05-11 14:55     ` Sébastien Rey-Coyrehourcq
2022-05-11 15:48       ` Julien Lepiller
2022-05-12  8:40         ` Sébastien Rey-Coyrehourcq
2022-05-12  9:28           ` Julien Lepiller
2022-05-12 12:32             ` Sébastien Rey-Coyrehourcq
2022-05-17  7:26               ` Daniel Meißner
2022-05-17  8:01                 ` Sébastien Rey-Coyrehourcq
2022-05-17  8:57                   ` Daniel Meißner
2022-05-17  9:20                     ` Sébastien Rey-Coyrehourcq
2022-05-17 10:15                       ` Daniel Meißner
2022-05-17 16:02                         ` Sébastien Rey-Coyrehourcq
2022-05-25 13:34                           ` Daniel Meißner
2022-05-25 18:45                             ` Efraim Flashner [this message]
2022-07-11  6:06                             ` Joshua Branson
2022-05-26  0:31                           ` Dominic Martinez
2022-06-01 20:38                             ` Sébastien Rey-Coyrehourcq
2022-06-12 19:32                               ` sebastien rey-coyrehourcq
2022-06-13 19:31                                 ` Dominic Martinez
2022-06-14 10:36                                   ` Sébastien Rey-Coyrehourcq
2022-05-11 21:56       ` Mekeor Melire

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=Yo55YnAKxhzWQF28@3900XT \
    --to=efraim@flashner.co.il \
    --cc=daniel.meissner-i4k@ruhr-uni-bochum.de \
    --cc=help-guix@gnu.org \
    --cc=julien@lepiller.eu \
    --cc=sebastien.rey-coyrehourcq@univ-rouen.fr \
    /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).