agenix
digga
agenix | digga | |
---|---|---|
10 | 23 | |
1,241 | 982 | |
- | 0.6% | |
7.3 | 2.4 | |
6 days ago | 9 months ago | |
Nix | Nix | |
Creative Commons Zero v1.0 Universal | 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.
agenix
-
password manager solution advice
How about: https://github.com/ryantm/agenix
-
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.
-
Ask HN: A Better Docker Compose?
I don't have a write-up, just my code in git. But it's not public. I'm not using anything out of the ordinary - Nix containers, modules, and functions, and the Agenix module with uses a private key to decrypt secrets at start. The Nix language is inherently composable. Here are some links that explain:
Containers:
https://nixos.wiki/wiki/NixOS_Containers
Modules:
https://nixos.wiki/wiki/NixOS_modules
Functions:
https://www.reddit.com/r/NixOS/comments/zzstun/please_help_m...
Agenix:
https://github.com/ryantm/agenix
-
ridiculously easy mail server setup with NixOS
For passwords I am using agenix which is also pretty awesome, an alternative could have been sops.nix.
-
NixOS for Apt/Yum Users: a Gift That Keeps on Giving
Alternatively, you could simply add the wireless connection files to the Networkmanager dir in /etc using environment.etc. Though keep in mind that any file declared in your config is readable by any user in your system. agenix would be the solution to that.
-
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.
-
Understanding nixos secrets management/aws configuration
Answering your broader question (secret management) colmena does that for me outside the Nix store. I also use git-crypt to store secrets in the repo. There are also more Nix-y alternatives like agenix.
-
If you’re not using SSH certificates you’re doing SSH wrong
I feel that trying to make SSH keys short-lived is becoming more painful each year because there's an increase of tools that use SSH keys for purposes other than SSH logins. For example, age [1] encrypts files with SSH keys, agenix [2] does secrets management with it, Git can now sign commits with it [3], and even ssh-keygen can now sign arbitrary data [4]. All of these become useless the moment you start using short-lived keys.
[1]: https://github.com/FiloSottile/age
[2]: https://github.com/ryantm/agenix
[3]: https://calebhearth.com/sign-git-with-ssh
[4]: https://www.man7.org/linux/man-pages/man1/ssh-keygen.1.html
-
homeage: declarative runtime decrypted age secrets for home manager
I built this because I try to keep as much as possible outside of my system config but all of the secret managers I found were system only. I had no idea how to solve this until I found RaitoBezarius' awesome pull request to agenix where it all clicked. It also exposed me to the inner workings of home-manager which has definitely made me appreciate it more! I kept this separate from agenix because I am interested only in a module rather than a CLI and thus see it as having a different fit.
-
How do you manage your private keys?
I've been thinking about the same thing. I haven't gotten around to it yet but agenix looked the most promising to me so far
digga
-
Looking for dotfiles repo examples
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.
-
(meme) It's a temporary setback really
https://nixos.wiki/wiki/Flakes, especially the “see also” section. If you’re looking to use for NixOS config across multiple hosts, digga (see the repo for example template) is pretty nice for encapsulating a lot of boilerplate.
-
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
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.
-
What's the proper way to set up nix / home manager w/ flakes, directory wise?
Yes, I put the repository in ~/nix. My repository is based on devos, but I am thinking of switching to a different setup, because I don't want to depend on a framework which can be an issue in updating.
-
The future of Home Manager and Flakes
I no longer use the official way since I have switched to flakes. I am currently using a devos-based config, which is a boilerplate that depends on a Nix toolchain, but I plan on rewriting the config with flake-utils-plus. You probably can install home-manager using deploy-rs. See the following comment:
What are some alternatives?
sops-nix - Atomic secret provisioning for NixOS based on sops
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
nixos-config - My NixOS configurations.
nixos-config - Mirror of https://code.balsoft.ru/balsoft/nixos-config
nixos - My NixOS Configurations
homeage - runtime decrypted age secrets for nix home manager
packages - Community maintained packages for OpenWrt. Documentation for submitting pull requests is in CONTRIBUTING.md
nix-darwin - nix modules for darwin
pass-import - A pass extension for importing data from most existing password managers
nixos-generators - Collection of image builders [maintainer=@Lassulus]