4 ms·
> A few examples of what you can do right now These examples look neat. I'm reminded of https://nix.dev/ https://nix.dev/ (which, sadly, is pre-flake). > make
by rgoulter 4y ago
> A few examples of what you can do right now
These examples look neat. I'm reminded of https://nix.dev/ https://nix.dev/ (which, sadly, is pre-flake).
> make it easy to create and share Nix and NixOS configurations
I could see a lot of value in the sharing/reading aspect of this. -- I think it'd be helpful to be able to look at different NixOS configurations without having to dig into the code directly.
> The site works directly with the Nix command line tool
I find this part confusing.
One of the neat things about nix flakes, is that it's "like docker without containers". You can just run `nix run github:<owner>/<repo>`, and nix will be able to run the code from that flake. -- So I guess I'd expect the "copy-paste to run this" command to be similar to "nix run https://mynixos.com/<whatever> https://mynixos.com/<whatever>".
But, the "Download" section in the Meta tab of the demonstrations are about using some tool that isn't nix.
- pveierland 4y agoThanks for the feedback! When released, the flakes are just tarballs which can be used with the Nix command line tool, for example nix develop https://api.mynixos.com/mynixos/demo-windows-devshell/archive/latest.tar.gz Will bring you into the development shell declared by the demo-windows-devshell flake. You can either copy the link for specific versions, or use the "Latest" reference link. These links can either be used with the Nix command line tool or as direct flake input URLs to flakes that you write outside of MyNixOS. Note that the commands shown in the "Meta" section are just shell scripts to help you install Nix, direnv, and a flake loader, which is just a convenience wrapper that you can keep in your source control if you wish.