digga
sops-nix
Our great sponsors
digga | sops-nix | |
---|---|---|
23 | 9 | |
977 | 1,187 | |
0.3% | - | |
2.4 | 9.1 | |
8 months ago | about 20 hours ago | |
Nix | Nix | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
digga
-
Looking for dotfiles repo examples
I am using the home-manager input define in the flake andas recommended by digga. I am using the home namespace:
I have been playing with digga for a few days in order to simplify my dotfiles repo. But I only got it half-working and there are little to no - useful - docs.
This one issue may clear things up, seems like my config is a little outdated: https://github.com/divnix/digga/pull/385
-
Building a highly optimized home environment with Nix
I'm new to the Nix world, but so far I've come across Divnix's Digga, Numtide's DevShell, and Misterio77's nix-starter-configs.
-
Need for a configuration framework?
There are config templates / configuration helper libraries that try to make this easier, for example digga/devos.
-
Sharing configuration between NixOS and MacOS
The digga library, while being more complex to use than other solutions here, got a pretty elegant solution for it merged a few weeks ago. Still some cracks that are getting smoothed over, but it seems to work.
-
Best practices for organizing code repository for multiple machines? What about deployment?
I like the concept digga/devos uses (unfortunately their stuff kind of is an overengineered incomprehensible mess): They use: - modules: for modules like in nixpkgs (i.e. stuff that defines options and generates configuration based on that options; are included into every host) - profiles: concrete configuration, can be included to host definitions - suites: sets of profiles (so you can for example have a desktop suite with all your profiles with "desktop" configuration options and apply that to all your desktop computers)
- Nix: An idea whose time has come
-
The Curse of NixOS
https://github.com/divnix/devos is something close to a framework.
I agree that language is too simple. Also I think some degree of IDE / language server support would help a lot. Refactoring modules, writing and importing custom functions was a bad experience for me - some arcane stacktraces were common, using repl was too verbose and with no clear way to debug whole configuration.
For the system, I like the devos template:
https://github.com/divnix/devos
The idea of flakes is how you define inputs, and you define the system (and packages, and shell etc.) in the outputs using the inputs. The inputs are git repos which point to other flakes. You can mix and match these as much as you want (see the devos repo for examples) and when you build the derivation, it generates a lockfile for exact commits in that point in time what were used in the given inputs.
You commit the lockfile and in the other systems where you pull your config from the repo, it uses exactly those commits and installs the same versions as you did in your other systems.
This was quite annoying and hard to do before flakes. Now it's easy.
The problem what people face with building their system as a flake is combining the packages so you can point to `jq` from the unstable nixos and firefox from the stable train. I think this aspect needs better documentation so it wouldn't be so damn hard to learn (believe me, I know). Luckily there are projects like devos that give a nice template for people to play with (with documentation!)
Another use for flakes is to create a development shell for your repo, an example what I did a while ago:
https://github.com/pimeys/nix-prisma-example
Either have `nix-direnv` installed, enter the directory and say `direnv allow`, or just `nix develop` and it will gather, compile and install the correct versions of packages to your shell. Updating the packages? Call `nix flake update` in the directory, commit the lockfile and everybody else gets the new versions to their shell.
sops-nix
-
Show me the way to cloud infra
For applications, I think environment variables are great. Especially if you adopt nomad because you could also use vault to populate secrets in. For machines that won't work so you'll need something else like https://github.com/Mic92/sops-nix
-
how to store secrets needed at install time
I've heard good things about and seen sops-nix used on a few really solid configs. Others tend to use Age or Homeage.
-
Nix way to recreate environments including authentication, configuration, etc?
You can use something like sops-nix if you're on NixOS https://github.com/Mic92/sops-nix.
-
Building a highly optimized home environment with Nix
Yeah, I don't know how to manage secrets yet. I've read about sops-nix, but I don't have the slightest clue how to integrate it into my own nix-config.
-
What would make NixOS more secure?
I use sops-nix for that. Secrets are stored encrypted in the store, and decrypted at runtime.
-
What to do...
One think I saw that I don't recommend is to change your password after installing; that's not very reporoducible, use users.users..hashedPassword or users.users..passwordFile with agenix or sops-nix.
- How to handle secrets in NixOS (for Docker container and Systemd Services)?
-
How do you manage your private keys?
So, I did some digging. According to the first Dicourse chat that popped up, it's "not possible". That's not an acceptable answer for me ;). I read through HM's appendix to see if there's a mention of private keys there (there weren't). I also know of SOPS (and sops-nix), but that seems to require an SSH/GPG key to decrypt :D.
-
A guide to build a Raspberry Pi cluster managed by NixOps
If you only need secrets management, there are quite a lot of bolt-on solutions with little overhead which are also agnostic to the form of deployment, like https://github.com/Mic92/sops-nix or https://github.com/ryantm/agenix. Personally for my machines I want unattended reboots, so I just copy all keys to the hard disk and manage secrets solely with file permissions.
What are some alternatives?
agenix - age-encrypted secrets for NixOS and Home manager
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
vault-secrets - NixOS tooling for Hashicorp Vault
nixos-config - Mirror of https://code.balsoft.ru/balsoft/nixos-config
nixos - My NixOS Configurations
nixfiles - My NixOS configuration and assorted other crap.
nix-darwin - nix modules for darwin
nixos-config - My NixOS configurations.
nixos-generators - Collection of image builders [maintainer=@Lassulus]
nixos - A fully automated replicable nixos configuration set
morph - NixOS deployment tool