mic92/dotfiles

My NixOS dotfiles

My personal bootstrap process

For bootstraping on legacy operating systems

Bootstrap dotfiles when having nix

$ nix run github:Mic92/dotfiles

Bootstrap homeshick without nix

$ nix-shell -p git
nix-shell> git clone --depth=1 https://github.com/andsens/homeshick.git $HOME/.homesick/repos/homeshick
nix-shell> alias homeshick="$HOME/.homesick/repos/homeshick/bin/homeshick"
nix-shell> homeshick clone https://github.com/Mic92/dotfiles.git

Bootstrap single user nix:

$ install -d -m755 -o joerg -g joerg /nix
$ curl https://nixos.org/nix/install | sh

Bootstrap multi-user nix:

$ curl https://nixos.org/nix/install -o install
$ sh ./install --daemon

Bootstrap home-manager

$ hm switch

Use my nvim configuration as a standalone without installing dotfiles

$ nix run 'github:Mic92/dotfiles#nvim'

Articles about my dotfile repo

• Explains basic structure: https://samleathers.com/posts/2022-02-03-my-new-network-and-deploy-rs.html

Need help with nix?

Drop me an email at [email protected] to book consultation on Nix/NixOS/DevOps related topics

dotfiles's Issues

Question: Folder-based secrets organization with sops

Hi, i recently observed how you are organizing secrets in /sops folder and I loved it. But some questions arise on me, how are you consuming that? I tried to find it in your code but I haven't found it.

I was, also, wondering if a module system like haumea could make it accessible to sops-nix or similar?

Thanks in advance from a follower of your amazing work!!

How do you deploy the `age` Private Key?

If my understanding is correct, the age Private Key is used to decrypt the secrets. This means it needs to be on the deployed system. Is this right?

If so, how do you deploy the key? Do you do it manually?

tasks.py

You might want to look into
https://github.com/go-task/task/tree/main

To simplify your tasks..

Deleting array-like openwrt uci config sections

dotfiles/openwrt/nix_uci/__init__.py

Line 109 in 05c0dbc

# HACK: there seem no better way to clear out a list

If you rely solely on uci batch commands, it's not possible to do. If you make use of some form of on-device scripting, it's trivial, and this is what both OpenWRT's documentation and scripts do currently. For example, deleting all existing network devices with ash:

while uci -q del network.@device[-1] 2>/dev/null; do :; done

There shouldn't really be much of an issue interspersing uci batch commands and segments of shell script; so long as you don't uci commit the changes until everything is done, any failure in the script won't be persisted and could be trivially reverted.

As a possibly more interesting alternative, ucode is now on every OpenWRT image from 22.03 and on, so you could directly ship the uci.json onto the router, along with a ucode script to parse & act on it directly on the target.

Question about home-manager

Hey @Mic92,
you have got an interesting and complex nix-setup. I forked to fiddle around with it and stumbled over your home-manager setup. Can you give me a hint, how it works? I would like to invoke it with a regular nixos-rebuild and just can not wrap my head around your setup. As I am always willing to learn, your answer would be very much appreciated.

[Thank You] Not An Issue

Hi Mic92,

I am new to Nix and was pointed to one of your repos today to solve a problem I was having while learning nix, and I have since found several great repos now, as well as this dotfiles repo to learn.

You rock, it is much appreciated. Thank you.

Question about things like "@LDAP_PASSWORD@"

dotfiles/nixos/eve/modules/bitwarden.nix

Line 8 in 5ec8984

ldap_bind_password = "@LDAP_PASSWORD@";

Is the real password substituted by a tool or something?