dotnix
digga
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.
dotnix
-
Ask HN: How do you sync your computers development configurations/environment?
home-manager and nix: https://github.com/legendofmiracles/dotnix
This allows me to abstract logic easily, have it all modular and have everything be nix.
-
How do you ensure the longevity of your customized Linux setup
If you’re interested and want to see more, here’s my massive configuration.
-
Raspberry Pi config for all things Internet
https://github.com/LegendOfMiracles/dotnix/tree/master/hosts... (bottom lines describe the remote build logic) this is the actual config of the pi... One other file also gets sourced: the defaults-nixos file in the root of the repo. And the distributed build host nix file describes creating a build user on my main machine.
The setup is mostly mirrored from https://sgt.hootr.club/molten-matter/nix-distributed-builds/
-
Can I see what packages have been updated?
Config is somewhere in HM/fish.nix :p https://github.com/legendofmiracles/dotnix
-
How do you manage your private keys?
https://github.com/legendofmiracles/dotnix inside the secrets dir
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?
nixos-search - Search NixOS packages and options
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
agenix - age-encrypted secrets for NixOS and Home manager
nixos-config - Mirror of https://code.balsoft.ru/balsoft/nixos-config
sops-nix - Atomic secret provisioning for NixOS based on sops
nixos - My NixOS Configurations
nvd
vscode-in-docker - Run VSCode inside of a Docker Container
nix-darwin - nix modules for darwin
nixos-generators - Collection of image builders [maintainer=@Lassulus]