homies
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.
homies
-
Show HN: Fleek – Own Your $Home
This is awesome! I utilize `nix` on Linux and Mac but I haven't "drank the kool-aid" so I utilize `nix profile` and a makefile:
https://github.com/sontek/homies/blob/master/justfile
Fleek basically replaces my hacked together work flow with something that I'd actually utilize on a daily basis! Nix shouldn't be an all or nothing thing and this is one step closer to making it a generally available set of technology.
-
Dotfiles Management
I see a lot of people mentioning home-manager / nix in the comments. I tried drinking the nix kool-aid and home-manager and all that was a little too much more me and landed on a hybrid approach:
https://github.com/sontek/homies
1. I use a `justfile` that calls `nix profile install ...` to install my packages, rather than using a nix configuration file. This allows me to use a standard package manager workflow rather than going "all in".
https://github.com/sontek/homies/blob/master/justfile#L24-L2...
2. I then use GNU Stow to install my dotfile configuration:
https://github.com/sontek/homies/blob/master/justfile#L93-L9...
I think this is a great middle ground where I can utilize `nix` as my package manager across Linux and Mac and have consistency while not having to learn the whole configuration language or change my workflow.
The other tools I use heavily in my environment:
- https://asdf-vm.com/: I find this better than installing python/node/etc from nix.
- https://github.com/casey/just: I use this as my command runner (similar to make but cleaner in my opinion)
-
Nix: An idea whose time has come
Yeah, I think its things like this that make it hard to adopt nix. All I want is a way to say "I want jq, kubectl, and terraform installed" and have it available globally. Not for specific projects or anything like that.
Right now I maintain a makefile that installs everything for me using `nix profile`:
https://github.com/sontek/homies/blob/master/justfile#L14-L2...
Which almost exactly like I want. Only issue is sometimes a new hash is generated (which I don't understand.. maybe a config update in the repos?) and the makefile can't run anymore:
error: packages '/nix/store/y65pp5hipid0fzxl1z7xjxdk4h9jwfw7-exa-0.10.1/bin/exa' and '/nix/store/gy0bqcs9mcan8af47wakdylhal67dpy4-exa-0.10.1/bin/exa' have the same priority 5; use 'nix-env --set-flag priority NUMBER INSTALLED_PKGNAME' to change the priority of one of the conflicting packages (0 being the highest priority)
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?
homer - The home directory management tool.
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
fleek - [deprecated] Own your $HOME
nixos-config - Mirror of https://code.balsoft.ru/balsoft/nixos-config
filetailor - Copy and modify plain text files between devices without templates
nixos - My NixOS Configurations
configs - Dot-files among other configs
sops-nix - Atomic secret provisioning for NixOS based on sops
dot-git - Managing your dotfiles the Git Way™
nix-darwin - nix modules for darwin
dotfiles - dotfiles + debian setup
nixos-generators - Collection of image builders [maintainer=@Lassulus]