get
+The get
subcommand is useful for getting a bare copy of nixflk without the
+git history. You can pull either the core or community branches.
Usage
+flk get BRANCH DEST-DIR
+
+If DEST-DIR is ommitted, it defaults to ./flk.
+ +From b95e6d326221892d71be8a7a256ac622ced0d2a3 Mon Sep 17 00:00:00 2001
From: nrdxp The devshell for the project incudes a convenient script for managing your
+system called Without any of the subcommands, Will build hosts/NixOS.nix. You can change out The This will install hosts/NixOS.nix to /mnt. You can override this directory
+using standard Making and writing an installable iso for This works for any file matching The As it sounds, this will update your lock file, and commit it. Nixflk is a template which grants a simple way to use, deploy and manage
-NixOS systems for personal and productive use. It does this by
-providing a sane repository structure, integrating several popular projects
-like home-manager, setting clear guidelines, offering useful
-conveniences, and eliminating boilerplate so you can focus on deploying your
-systems. There are two branches from which to choose: core and
-community. The community branch builds on core and includes
-several ready-made profiles for discretionary use. Every package and NixOS profile declared in community is uploaded to
-cachix, so everything provided is available without building
-anything. This is especially useful for the packages that are
-overridden from master, as without the cache, rebuilds are
-quite frequent. Nixflk leverages the flakes feature available via an experimental
-branch of nix. Until nix 3.0 is released, this project should be
-considered unstable. Nixflk is licensed under the MIT License. If making a change to core, or adding a feature, please be sure to update the
+relevant docs. Each directory contains its own README.md, which will
+automatically be pulled into the mdbook. The book is
+rendered on every change, so the docs should always be up to date. While much of your work in this template may be idiosyncratic in nature. Anything
+that might be generally useful to the broader NixOS community can be synced to
+the If you wish to contribute please follow these guidelines: format your code with The commit message follows the same semantics as nixpkgs.flk command
+flk
. Each of the following chapters is a reference for one of
+its subcommands.Rebuild
+flk
acts as a convenient shortcut for
+nixos-rebuild
:
+flk NixOS build
+
build
for switch
, test
,
+etc. Any additional arguments are passed through to the call to
+nixos-rebuild
.Usage
+flk help
+
install
+install
subcommand is a simple convenience for nixos-install
, similar
+to the shortcut for nixos-rebuild
, all additional arguments are passed
+through.Example
+
+flk install NixOS
+
nixos-install
args.ISO
+hosts/NixOS.nix
is as simple as:
+flk iso NixOS
+
+dd bs=4M if=result/iso/*.iso of=/dev/$your_installation_device \
+ status=progress oflag=sync
+
hosts/*.nix
excluding default.nix
.update
+update
subcommand is a simple alias for:
+nix flake update --recreate-lock-file --commit-lock-file
+
Introduction
-Community Profiles
-⚠ Advisory
-License
-Pull Requests
+Community PRs
+community
branch to provide a host of useful NixOS configurations available
+"out of the box".Style
+
+
nixpkgs-fmt
. The default devshell
+includes a pre-commit hook that does this for you.
+
+#
symbol to specify ambiguities. For example,
+develop#zsh: <rest of commit message>
would tell me that your updating the
+zsh
subprofile living under the develop
profile.