impermanence
nvd
Our great sponsors
impermanence | nvd | |
---|---|---|
33 | 4 | |
878 | - | |
10.4% | - | |
5.9 | - | |
about 2 months ago | - | |
Nix | ||
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.
impermanence
-
Tvix – A New Implementation of Nix
I would not call these projects unbelievable, but they are neat.
- Opt-in state: https://github.com/nix-community/impermanence and https://grahamc.com/blog/erase-your-darlings/
-
Silverblue users: why?
This is indeed a blind spot. Thanks for pointing that out! Silverblue -to my knowledge- doesn't do a lot to address this. Though, 3rd-party tools like Home Manager and the suite of applications developed by the folks over at uBlue might be able to limit this to a minimum. Though I'm not sure if it surpasses NixOS in this regard; for the uninitiated. Though, to my knowledge, this requires special attention and depends on the specifics of the NixOS system in question.
- NixOS for the Impatient
-
Interested in NixOS, have some questions
Some files in /etc (like saved networks) will still not be managed by NixOS, if you want to have full control over them use Impermanence
-
Upgrading to NixOS 22.11 Issue
{ imports = [ (modulesPath + "/installer/scan/not-detected.nix") "${builtins.fetchGit { url = "https://github.com/NixOS/nixos-hardware.git"; }}/system76" "${builtins.fetchGit { url = "https://github.com/nix-community/impermanence.git"; }}/nixos.nix" ];
-
Good guides for a non-developer using NixOS?
There is a maintained collection of modules for running this kind of NixOS setup. It's called impermanence.
-
48hrs with Fedora Silverblue and I'm SOLD. Question: does anyone else use a volatile home ?
https://grahamc.com/blog/erase-your-darlings https://nixos.org/ https://github.com/nix-community/home-manager https://github.com/nix-community/impermanence
-
First post, here's my home lab and how I use it every day (running Proxmox and NixOS)
I'm also fascinated by the idea of completely decoupling the state from the configuration using https://github.com/nix-community/impermanence. If you can get your system working without leftover state sticking around, and continuously back up the state you do have, you're almost guaranteed to have a fully working environment at all times.
-
First post, here's what my homelab does running Proxmox and NixOS
Drop Proxmox for vanilla NixOS + kvm. Working towards impermanence to manage persistent state everywhere.
-
Nix: Taming Unix with Functional Programming
docs nixos: https://nixos.org/manual/nixos/stable/
This tooling includes higher-level helpers for language-/environment-specific packaging, like "buildGoModule", "buildRustPackage" and so on, as well as e.g. tooling to run integration tests in a whole cluster of inter-connected linux VMs!
Packages which are submitted to nixpkgs must fulfill certain criteria, such as not using "IFD" (input-from-derivation, to simplify: "letting nix evaluate nix-code which was generated by another deriviation/"nix package".
nixpkgs is alive and well with lots of daily contribution and an everlasting effort to keep Hydra, the nix-specific CI/CD system and public binary caches up to date and responsive. Thanks to all maintainers & contributors!
* flakes are an approach to standardize a way to package nix code outside of nixpkgs but to still keep it re-usable. They are still "experimental" as the details are figured out, but nevertheless used in production. There are some frame-works to keep boilerplate low, like "flake-utils", "flake-parts" and others, as well as e.g. deployment tools like "colmena" and "deploy-rs" and re-usable helpers for system-configuration like e.g. https://github.com/nix-community/impermanence
There's lots of other stuff in the community, things like home-manager, direnv + flakes and devshells changed my workflow fundamentally to the better since I've switched. If you got the time and are still interested, join us on matrix or elsewhere :)
nvd
-
First post, here's my home lab and how I use it every day (running Proxmox and NixOS)
And this repo:https://gitlab.com/khumba/nvd
-
The Curse of NixOS
There's nothing there that needs flakes (an experimental feature which people should not enable without understanding the implications). You could build a system derivation and run a diff against /run/current-system on it.
For what it's worth, nix-diff has very verbose output (it literally diffs everything that is different in the inputs & outputs). A slightly nicer way to diff systems is nvd[0] (example output[1]) which only shows version changes and added/removed packages.
[0]: https://gitlab.com/khumba/nvd
[1]: https://deploys.tvl.fyi/diff/4xmyvkr9nw0cwkn5q38p0cfc58x3jdy...
-
Can I see what packages have been updated?
And it uses https://gitlab.com/khumba/nvd to diff the revisions
What are some alternatives?
home-manager - Manage a user environment using Nix [maintainer=@rycee] [Moved to: https://github.com/nix-community/home-manager]
nix-config - Nix configurations
nixpkgs - My Nix system configs!
raspi-overlayroot - Protect your SD card against wear and tear
nix-config - :space_invader: NixOS configuration
dotfiles - My personal dotfiles
nix-config - Personal nixos and home-manager configurations.
nix-prisma-example - An example Prisma project using nix
nix-embedded - Nix embedded image generator.
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
dotfiles - My PC Dotfiles & Website
nix - Nix, the purely functional package manager