lorri
std
lorri | std | |
---|---|---|
6 | 5 | |
998 | 361 | |
- | 2.2% | |
0.0 | 8.8 | |
almost 2 years ago | about 1 month ago | |
Rust | Nix | |
Apache License 2.0 | - |
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.
lorri
-
NixOS + Haskell best practices circa March 2023
lorri
- Lorri: Project's Nix-Env
-
niv, naersk, napalm: moving on
And how does niv compare to https://github.com/target/lorri
-
A treatise on Nix
Yes, you can "hold on", it's called gcroots. There's lorri which you can also use to defer the tediousness of managing the gcroots to a daemon.
-
Per process memory and CPU usage control
Not that I know of but if you are having trouble with rebuilding and running out of memory, maybe the solution would be to cache the builds locally? You could use lorri to cache your development builds (https://github.com/target/lorri).
-
NixOS Linux
> Using a special command (nix-shell) whenever I needed to do development things (e.g. Rust builds) was not my idea of fun.
Funny you should mention that, because that's exactly what got me using Nix everywhere :). I've always hated installing tools and libraries globally—what if I need a different version for a future project?—so I like tools that sandbox as much as possible like virtualenv, cargo, cabal... etc. But these tools are all language-specific and have their own limitations (especially around native libraries and dependencies written in other languages).
nix-shell gives me the equivalent of virtualenv that works for everything. I can have a single sandboxed environment even if my project uses a bunch of different languages and I can manage everything in a reproducible, low-overhead fashion. No more worrying about making a mess by installing tools or packages globally.
Then, once I got really used to that, I spent some time setting up direnv[1] and lorri[2]—both of which are themselves managed with Nix, of course!—so that my environment gets automatically configured as soon as I enter a project directory without needing to call nix-shell explicitly. To be honest, the experience is still a bit rough, but it works well enough day-to-day that I have my reproducible sandbox cake and eat it in an mostly frictionless way too :).
[1]: https://direnv.net/
[2]: https://github.com/target/lorri
std
-
Nix is a better Docker image builder than Docker's image builder
Newcomer here. Could anyone tell if std [0] is a good way to bring more sanity into flake design, esp. in avoiding ivory towery custom approaches? Using devenv.sh is another option, but I liked emphasis on having a common mental picture and focus on SLDC that std provides.
[0] https://std.divnix.com
-
Show HN: Flox 1.0 – Open-source dev env as code with Nix
Agreed on the experience, hard to onboard. I looked at devenv.sh as easier way to get going. Implemented all with Nix, less lock-in. Just found std [0] and that quote looks promising too.
[0] https://std.divnix.com/
-
NixOS + Haskell best practices circa March 2023
std/paisano for large projects.
- Std: The Nix Flakes framework for perfectionists with deadlines
- Nix: Taming Unix with Functional Programming
What are some alternatives?
direnv - unclutter your .profile
deploy-rs - A simple multi-profile Nix-flake deploy tool.
nix - Nix, the purely functional package manager
awesome-nix - 😎 A curated list of the best resources in the Nix community [maintainer=@cyntheticfox]
nix-direnv - A fast, persistent use_nix/use_flake implementation for direnv [maintainer=@Mic92 / @bbenne10]
hydra - Hydra, the Nix-based continuous build system
nixops - NixOps is a tool for deploying to NixOS machines in a network or cloud.
poetry2nix - Convert poetry projects to nix automagically [maintainer=@adisbladis]
nickel - Better configuration for less
adcomp - AD computation with Template Model Builder (TMB)
dotfiles - i3 + Plasma: using the i3 window manager on the top of KDE Plasma and other dotfiles, configurations, scripts, workarounds and practises from my Debian Sid machines.
nixpkgs - Nix Packages collection & NixOS