Home Manager using Nix
nix
Our great sponsors
Home Manager using Nix | nix | |
---|---|---|
182 | 370 | |
5,821 | 10,814 | |
5.6% | 6.1% | |
9.8 | 10.0 | |
4 days ago | 2 days ago | |
Nix | C++ | |
MIT License | GNU Lesser General Public License v3.0 only |
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.
Home Manager using Nix
-
Cosmic Desktop: Hammering Out New Cosmic Features
It's probably overkill for what you are trying to do. But I have been using home-manager [0] as a way to quickly restore my working environment.
-
How do I actually update home-manager?
$ home-manager --version 23.05 $ nix-channel --add https://github.com/nix-community/home-manager/archive/release-23.11.tar.gz home-manager $ nix-channel --update $ nix-shell '' -A install [...] All done! The home-manager tool should now be installed and you can edit /home/MY-USERNAME/.config/home-manager/home.nix to configure Home Manager. Run 'man home-configuration.nix' to see all available options. $ home-manager --version 23.05
-
Possible to use KDE plugins on nixos?
Unfortunately until we find more volunteers in this area, it is hard to see status quo changing. See also https://github.com/nix-community/home-manager/issues/607 and this ongoing project https://github.com/pjones/plasma-manager
- Exclude packages in home manager
-
An Overview of Nix in Practice
> Channels are, AFAIU, a reference to some point-in-time/commit/version of nixpkgs
It's not specifically nixpkgs, but any Nix code generally.
Per the Nix manual[0]:
> Channels are a mechanism for referencing remote Nix expressions and conveniently retrieving their latest version.
e.g. home-manager's suggested channel is just the github tarball for the relevant branch[1]:
nix-channel --add https://github.com/nix-community/home-manager/archive/master.tar.gz home-manager
-
Fake recruiter Lazarus lured aerospace employee with trojanized coding challenge
It sounds like you'd benefit a lot from Nix/NixOS [1], if not just home-manager[2].
-
Noob question: Where home-manager config after installed on archlinux
nix-channel --add https://github.com/nix-community/home-manager/archive/master.tar.gz home-manager nix-channel --update nix-shell '' -A install
-
Need help on home manager neovim config
I'm using flakes and home manager and not really sure how to go about managing my neovim configuration. I've read through some other posts, github issues, and various articles trying to suss out a good way to do this. Reading through other people's configs and posts was somewhat helpful but there is a lot going on I don't understand and everyone's examples I've seen vary wildly.
-
Recurring 'Home Manager not found' Error After Running nix-collect-garbage"
Said store path contains the home-manager repo. After the home-manager run, the store path is recreated.
-
I want to like NixOS but... I can't and I need some help
I can't answer all your questions, but home-manager does have a dconf module that would probably be better to use than that external tool. Everything inside the options block are the things you can pass to the dconf module.
nix
-
Tvix – A New Implementation of Nix
(Nix itself is slowly chugging along with Windows via MinGW - https://discourse.nixos.org/t/nix-on-windows/1113/108 and https://github.com/NixOS/nix/issues/1320 , for example.)
-
Colima k8s nix setup
Nix is a cross-platform package manager. It uses the nix programming language. Nix and NixOs are often used in the same context, but while the first is a package manager, the latter is a linux distribution based on nix.
-
NixOs - Your portable dev enviroment
Today I want to talk to you about Nixos. What is it? Nixos is a declarative and reproducible OS, partly taking the words used on their own page. What does that mean?
-
Nix – A One Pager
Software developers often want to customize:
1. their home environments: for packages (some reach for brew on MacOS) and configurations (dotfiles, and some reach for stow).
2. their development shells: for build dependencies (compilers, SDKs, libraries), tools (LSP, linters, formatters, debuggers), and services (runtime, database). Some reach for devcontainers here.
3. or even their operating systems: for development, for CI, for deployment, or for personal use.
Nix provision all of the above in the same language, with Nixpkgs, NixOS, home-manager, and devShells such as https://devenv.sh/. What's more, Nix is (https://nixos.org/):
- reproducible: what works on your dev machine also works in CI in prod,
- declarative: you version control and review your configurations and infrastructure as code, at a reasonable level of abstraction,
- reliable: all changes are atomic with easy roll back.
-
Tools for Linux Distro Hoppers
Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.
-
Ask HN: Could Nix make crypto mining more efficient?
- it reduces bloat, because you can generate an environment or OS image with only the software needed to run a specific program or service
My guess is that a big efficiency gain would come from the second point, because you don't waste CPU on code that you don't use.
Does this make sense? Has anyone explored this?
[0]: https://nixos.org
-
Go + Hypermedia - A Learning Journey (Part 1)
1) Setting up the development environment - I currently use devcontainers for most things, but may also dig into nix -> isolated, portable, repeatable development environment 2) Exploring Echo - understand routing, requests, response, etc. 3) Incorporate Templ - integration with Echo, template composition, etc. 4) Integrating TailwindCSS - config for use with Echo/Templ, development cycle, deployment, etc. 5) Add in HTMX - endpoints, template structure, concepts, etc. 6) hyperscript for interactivity - client side interactivity
-
Nixing Technological Lock In
"Your greatest challenge lies ahead -- and downwards..."
Oh, wait a second, my bad, that's the quote on the box cover for Zork I: (
https://upload.wikimedia.org/wikipedia/en/a/ac/Zork_I_box_ar...
https://en.wikipedia.org/wiki/Zork
)
What you really wanted was a link to where you could download Nix/NixOS -- and/or learn more about it!
Here ya go!
"Your greatest challenge lies ahead -- and downwards..."
:-) :-)
I say all of the above in the spirit of humor -- and as a NixOS user and fan!
(But yes, there is a learning curve to it, so yes, learning Nix/NixOS could be a challenge!)
((But you're a bright person, you have Google and ChatGPT to assist you, and you like challenges!))
-
What it was like working for Gitlab
Semi-related, I would recommend to anyone who is a Linux native to try to find some kind of "minimum viable setup" that is really really easy for you to run out of VirtualBox or Parallels or something for this reason. No matter where you go, you know you can have a suite of tools which work just as you want them to there. Being able to tear it down and rebuild it quickly is also a great way to deal with debugging certain kinds of problems of the "it runs/doesn't run on my machine" category.
How you do this is of course up to you. At one end of the spectrum is just relying on your memory. At the other end is using NixOS https://nixos.org/ to get fully reproducible builds anywhere you go. Between these are a vast field of options. I know a guy who maintains an Ansible file set to `host: localhost` which installs everything he wants from that file. For me, I just stick with the latest Ubuntu version and maintain a few shell scripts [1] that install 80% of what I like to have on a new install.
If you like the scientific approach, you can install something like https://atuin.sh/ and do some statistics on what programs you actually run most frequently based on your long term shell history.
-
Cloudflare R2-Backed Nix Binary Cache on Fly.io
See https://github.com/NixOS/hydra/issues/838 for making content-addressed derivations supported by hydra.nixos.org. At that point, we can actually try out the XP feature at scale.
Also see https://github.com/NixOS/nix/issues/8919 for this accepted RFC
Once those things are done, we can get back to merging in the IPFS code.
Now that there is an Nix team and I am on it, there is much, much less of an issue of these experiments being caught in limbo :).
What are some alternatives?
Ansible - Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy and maintain. Automate everything from code deployment to network configuration to cloud management, in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com.
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
GNU Stow - GNU Stow - mirror of savannah git repository occasionally with more bleeding-edge branches
distrobox - Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
nixos-flake-example - This is a demo NixOS config, with optional flakes support. Along with notes on why flakes is useful and worth adopting.
void-packages - The Void source packages collection
NixOS-WSL - NixOS on WSL(2) [maintainer=@nzbr]
flatpak - Linux application sandboxing and distribution framework
emacs-overlay - Bleeding edge emacs overlay [maintainer=@adisbladis]
homebrew-emacs-plus - Emacs Plus formulae for the Homebrew package manager
chezmoi - Manage your dotfiles across multiple diverse machines, securely.
guix - Read-only mirror of GNU Guix — pull requests are ignored, see https://guix.gnu.org/en/manual/en/guix.html#Submitting-Patches instead