Conversation
Flake documentions in its own file, so as not to scare the normies. + Installation instructions + System package details + Running Live, installing plugins, etc. + Other flakes and options + Sample system config Couple of links to the flake documentation in the README, * Push NixOS users to FLAKE.md in the Installation section * Push Flake users to the appropriate section in FLAKE.md for installing vsts
|
Thank you so much for this! |
|
@LennartMeer good catch, you should open an issue with the details you can provide! Only planning on documentation in this PR, so an issue would ensure the bug is properly documented. It may be worth adding |
Updated wording for clarity and corrected typos in FLAKE.md.
Fixes a couple typos. Adjusts wording to clarify meaning. Fix claim that every commit will cause a rebuild of wine, this is not true, Nix is smarter than that.
Replaced instances of `.#` with `#` in documentation, based on V33's feedback. Replaced instances of `nix run .#` with `nix run github:shibco/ableton-linux` for consistency, despite the bulkiness.
|
Thanks to @Version33 for pontificating on nix vocabulary, and especially @r3quisitevariety for reviewing and refining the docs. I've tested all the commands excepting the Realtime flake option, and am fairly confident in the accuracy of this documentation. Ready for review. |
Co-authored-by: fernwick <229844000+fernwick@users.noreply.github.com>
4 participants
Basic documentation for the nix flake. I put the documentation in a separate file,
FLAKE.mdin the main directory, to not clutter the README.In two locations in the README I direct NixOS/flake users to the flake documentation.
Nix-heads who are smarter than me: Have I screwed up any terminology? Does it make sense? I use
.#flake-namea few times, is the.a proper way to reference the flake in this usage, or should I just use#flake-name?If I get a few thumbs up from nix users, I'll mark this for review.