nix-processmgmt
napalm
Our great sponsors
| nix-processmgmt | napalm | |
|---|---|---|
| 6 | 2 | |
| 236 | 101 | |
| - | 2.0% | |
| 3.7 | 6.1 | |
| 5 months ago | 4 months ago | |
| Nix | Nix | |
| MIT License | 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.
nix-processmgmt
-
What does the minimal version of NixOS consist of?
I somewhere saw this project being mentioned: https://github.com/svanderburg/nix-processmgmt
-
Avoiding Complexity with Systemd
That's nice and it showcases how Nix can create a declarative process management atop a script-based imperative manager. How is your experience with it? Also note that there's https://github.com/svanderburg/nix-processmgmt, a manager agnostic processes management framework supporting s6 among others, but your way seems a bit more straightforward.
-
is it possible to use nix on a non-systemd distro like void or artix?
There's a project still being developed: https://github.com/svanderburg/nix-processmgmt my understanding is that if home-manager would use it (I don't know if there is even plan to do that, it's not the same author), it would be able to work without needing systemd.
-
NixOS 21.05 Released
(builtins.fetchTarball "https://github.com/svanderburg/nix-processmgmt/archive/6def8584c6b028c922c550859a07b989d21d6f73.tar.gz")
-
Using nix-shell instead of docker-compose
It's not really clear to me what you are asking. Are you maybe looking for nix-processmgmt? (NixCon 2020 talk: https://cfp.nixcon.org/nixcon2020/talk/TW79FU/)
napalm
-
niv, naersk, napalm: moving on
I created https://github.com/nmattia/napalm/issues/34 and https://github.com/nmattia/naersk/issues/183 to move them to nix-community
-
NixOS 21.05 Released
Sure. NPM is the easy case because the package-lock.json file can easily be read by Nix and contains hashes for all of the packages. This means that simply be importing the file into Nix you can have a reproducible build. No Nix-specific maintenance required.
In the linked case I use this library to manage that https://github.com/nmattia/napalm (in that example I use master but for production I would pin a version). It simply parses the package-lock.json, downloads the packages and uses npm to build the node_modules folder. It also provides some convenient functions for building packages with "bin" files or just linking node_modules inside a build.
Note that this is more for project development. It doesn't use the "system" packages (intentionally) for Node, it fetches whatever versions you have specified from NPM. Nix will only provide the "native" stuff like Node and NPM themselves and any native libraries.
What are some alternatives?
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
nixGL - A wrapper tool for nix OpenGL application [maintainer=@guibou]
flake-utils-plus - Use Nix flakes without any fluff.
nix - A declaratively managed computing environment for rraval
NixOS-docker - DEPRECATED! Dockerfiles to package Nix in a minimal docker container
naersk - Build Rust projects in Nix - no configuration, no code generation, no IFD, sandbox friendly.
emacs-overlay - Bleeding edge emacs overlay [maintainer=@adisbladis]
nixos-shell - Spawns lightweight nixos vms in a shell
s6 - The s6 supervision suite.
archbox - Easy to use Arch Linux chroot environment with some functionalities to integrate it with your existing Linux installation. Mirror of https://momodev.lemniskett.moe/lemniskett/archbox
nix-direnv - A fast, persistent use_nix/use_flake implementation for direnv [maintainer=@Mic92 / @bbenne10]