The configuration of my operating system, Guix Linux, and day-to-day software (who are we kidding, emacs) defined in literate configuration style.
- The .org files represent the code itself.
- Makefile is used to tangle the code into seperate files of which are primarily Scheme, ELisp, and shell scripts.
- Finally, the Guix daemon interprets these files to generate everything from my desktop and laptop, to servers running in a rack or VMs inside of a hypervisor. (coming soon)
No more traditional dotfiles. Hello Scheme and literate configuration.
Important
I moved to Nix at the end of 2021, so this repository is no longer being maintained. However, I hope it still serves as an example to others exploring literate configuration and Guix.
With everything defined in this way I can treat my system as one program. It's 100% reproducible, bit by bit. My environments across laptop and desktop are exactly the same, staying in sync without headache. This is the way.
Every change to my system is now deployed from the Guix Store thanks to Guix Home. This means I get rollbacks, transcational upgrades, fine-grained profiles, and other guix goodness with even my dotfiles.
Other advantages:
- theming now becomes easier. It's all here, I can define one set of colors, fonts, or margins to be used everywhere. Technically possible before but again, don't want to pull my hair out.
- no more "polutting" my system with experiments. I can try different blockchain projects, work with a client that needs .NET, or do anything I want without feeling like I need to clean it up later.
- Scheme is fun to hack on, and I hack on my home-lab for fun
Learn more about Guix here.
This project isn't intended for outside use yet; please just use as an example. I use Makefile to tangle org files into their own configs and then guix system reconfigure to inject those config files into .config, create symlinks, set environment variables, etc.
$ make$ make installI use inheritance to share configuration between my machines where it makes sense. This is subject to change as I make progress, acquire new machines, setup new VMS, etc.
Base definition of machines I'll work on day-to-day. Includes core system functions like the kernel, libinput, X Window System, etc. This is to seperate configuration concerns from machines I have running in my home-lab, but keep things shared between my Desktop and Laptop.
Sensible definitions for my Desktop machine that are likely to never change. Includes Openbox configuration, users and filesystems for Desktops, more dotfiles and package configuration.
Felix is my Desktop computer sitting in my office at home. This file contains a lightweight Operating System definition and an extensive Guix Home definition, as well as some associated dotfiles, initialization scripts, etc. I don't store anything meaningful in my Home directory (it's all kept in /data), so this script manages 100% of my it.
Emacs is my editor and primary interface for using my computer day-to-day. This config is large, also defined in literate style, but does not get built beforehand like the rest of this repo. Changes are still deployed via the Guix Store but it is interpreted as Elisp at runtime.
- Feedback or questions? Find me on Twitter.