[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: It's time to build "guix deploy"
From: |
Pjotr Prins |
Subject: |
Re: It's time to build "guix deploy" |
Date: |
Thu, 14 Feb 2019 17:55:11 +0100 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
On Thu, Feb 14, 2019 at 04:35:47PM +0100, Giovanni Biscuolo wrote:
> the very reason I'm here is I don't want to use *anymore* *any* of them,
> with all due _respect_ for the venerable projects, your included!
I did not intend to push my 'solution'. I want to get away from that
too!
> I've used Puppet and some Ansible, studied CFengine and Salt
> Stack... then discovered Nix and rigth next Guix: what else? :-)
>
> [...]
>
> > and the emacs files sit in a git directory in the same tree and get
> > copied across running 'deploy emacs.yaml'.
>
> yes, we still miss "stateless user services config" (Pierre Neidhardt
> wrote an interesting summary here
> https://lists.gnu.org/archive/html/guix-devel/2019-02/msg00128.html)
>
> I'd like to be able to declaratively manage a *stateless* .config/
> instead of managing configuration with dotfiles [2]
>
> anyway Guix is _perfect_ to declare and deploy system services, what we
> miss is a little more abstraction (from operating-system to
> infrastructure?) and remote control of "guix system reconfigure"
>
> am I missing something?
I think you misread my E-mail. No doubt my fault ;).
Pj.
- Re: It's time to build "guix deploy", (continued)
Re: It's time to build "guix deploy", Christopher Lemmer Webber, 2019/02/12