grhmc

13 ms·

91.
by grhmc 3y ago
Yep, that should work! Give it a try and let us know how it goes. Come join us on Discord, we'd be glad to chat about it.
92.
by grhmc 3y ago
We don't have one yet, but watch for one in the coming weeks. The CLI we're putting together allows for searching and adding to your flake. You can search on the web UI, though: https://flakehub.com/search
93.
by grhmc 3y ago
Yeah, thanks. We only support GitHub Actions because of the authentication model it offer with JWTs. We're planning on expanding to support other forges, and eventually local publishing, too. In the meantime, you could use a GitHub act
94.
by grhmc 3y ago
Good question. Publishing to FlakeHub makes an archive of the release, checks to make sure it evaluates cleanly in isolation, and publishes it to FlakeHub's storage. This is to make sure that releases stay available in the long term, e
95.
by grhmc 3y ago
Hey HN, glad to see FlakeHub posted so eagerly! I have another thread over here: https://news.ycombinator.com/item?id=37224148 We built FlakeHub to bring SemVer and a crates.io-like experience to Nix and flakes. Please chec
96.
by grhmc 3y ago
Hey folks, Graham -- CEO of DetSys here. So glad to be able to share FlakeHub, our most ambitious project yet. FlakeHub brings a crates.io-like experience to Nix and flakes, with semver releases and publish-time checks to make sure the flak
97.
Show HN: FlakeHub – Discover and publish Nix flakes(flakehub.com)
154 points by grhmc 3y ago|107 comments
98.
by grhmc 3y ago
It is great to hear about your work in the space! Several years ago I looked at implementing a custom component for k8s which would exchange nix store paths instead of containers, substitute, and bind mount them in at run time. It was an in
99.
by grhmc 3y ago
"It depends." poetry2nix is pretty good! Generally, exporting to an OCI image, or targeting a production environment that can run Nix closures natively is the way we go about it. Many of our services use buildLayeredImage[0] and t
100.
by grhmc 3y ago
Yep, that works great for cases where you trust all your contributors. We do the same for some projects internally, too. However, for public projects where you don't it gets a bit ... dicier. Glad to hear that's working for you!
101.
by grhmc 3y ago
Great question. Yes. Anything that Nix builds during your workflow will get cached. Give it a try and let me know how it goes?
102.
by grhmc 3y ago
Nice! Yeah, we're obviously big fans of NixOS over here :). In cases where build infrastructure is highly ephemeral, this sort of cache would make a lot of sense. We'd love to help get it working there!
103.
by grhmc 3y ago
I'm not sure... want to open a ticket? :)
104.
by grhmc 3y ago
Check out https://zero-to-nix.com/concepts/closures and https://zero-to-nix.com/concepts/realisation , which I think add more color to this (and also is largely authored by biggestlou here.)
105.
by grhmc 3y ago
Nix's design gives good guarantees about reproducibility. It may not be bit-perfect, but in general it is _very_ good. Maybe the Zero to Nix article on Caching, and its linked pages will help? https://zero-to-nix.com/co
106.
by grhmc 3y ago
One project cut their CI time from 18m to 3m: https://github.com/awkward-squad/hasql-interpolate/actions . I wonder who will see the biggest cut! Note that when PRs merge to the default branch, their cache doesn&#x
107.
by grhmc 3y ago
I think it should be pretty straightforward to make the Magic Nix Cache work on GitLab, too. They have a similar caching API. We'll take a look!
108.
by grhmc 3y ago
Graham Christensen here, cofounder of DetSys. Happy to answer any questions! The Magic Nix Cache has been a huge boon to us internally, and we're really excited to share it with the world today.
109.
by grhmc 4y ago
I certainly feel that way.
110.
by grhmc 4y ago
I'm delighted to see your edit :). Our installer makes a few configuration choices that upstream doesn't, but the main driving goal for us is to be reliable, safe, and easy to undo.
111.
by grhmc 4y ago
This is such a good summary of all the issues we've been running into over and over, and part of the deep motivations of our work here.
112.
by grhmc 4y ago
I commented elsewhere in the thread, but we have an open issue for SELinux support: https://github.com/DeterminateSystems/nix-installer/issues/1... . Hopefully we can get that rolling soon.
113.
by grhmc 4y ago
Thanks! The end result is not quite the same. For example, we turn on flakes, nix-command, and make a couple other minor tweaks to the Nix configuration to make what we think are user-friendly improvements. For example: https://g
114.
by grhmc 4y ago
I wonder if you've tried our installer? Part of its reason for existing is the ability to safely / completely uninstall.
115.
by grhmc 4y ago
Thanks for calling that out. Our installer (and the upstream installer) don't support SELinux yet, but there is work in that direction. Here's our tracking issue: https://github.com/DeterminateSystems/nix-inst
116.
by grhmc 4y ago
I'd recommend: 1. Start learning with https://zero-to-nix.com/ 2. Take a look at https://github.com/nix-community/home-manager Good luck!
117.
by grhmc 4y ago
I've seen some of those changes from DavHau before, they're good! We've also been looking at the statically built version of Nix which is good for "single user" / home-directory-managed installs of Nix. It&#x27
118.
by grhmc 4y ago
We're working on broadening the use-cases that Nix is appropriate for. Things like https://zero-to-nix.com/ , https://www.riff.sh/ , and the Determinate Nix Installer's goal is to make installing Ni
119.
by grhmc 4y ago
Whew, let's go. On NixOS: I generally agree, though it can be tricky to get that done with NixOS. I bet we can make some inroads there. Easy questions: > idempotent It isn't currently idempotent, but we're working on &quot
120.
by grhmc 4y ago
Graham here, CEO of DetSys. I'd be happy to answer any questions I can about the new installer and what we're up to!

More ›