foodogsquared/nixos-config
1
0
Fork 0
mirror of https://github.com/foo-dogsquared/nixos-config.git synced 2025-04-19 06:19:12 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs/site: add "disko" to "Project-specific setup"

Browse Source
This commit is contained in:
Gabriel Arazas 2023-07-09 18:27:39 +08:00
parent df26062cd1
commit 10a047358e
No known key found for this signature in database
GPG Key ID: ADE0C41DAB221FCC
2 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/content/en-US/menu.adoc
View File

@ -16,6 +16,7 @@
* NixOS modules * NixOS modules
** link:{{< relref "./nixos-modules/profiles" >}}[Profiles] ** link:{{< relref "./nixos-modules/profiles" >}}[Profiles]
** link:{{< relref "./nixos-modules/workflows" >}}[Workflows] ** link:{{< relref "./nixos-modules/workflows" >}}[Workflows]
** link:{{< relref "./nixos-modules/disko" >}}[disko]
* link:{{< relref "./using-parts-of-my-configuration" >}}[Using parts of my configuration] * link:{{< relref "./using-parts-of-my-configuration" >}}[Using parts of my configuration]

24
docs/content/en-US/nixos-modules/disko/index.adoc Normal file
View File

@ -0,0 +1,24 @@
---
title: disko
---
= disko
This configuration uses github:nix-community/disko[opts=repo] extensively for creating them filesystem configurations and automating them filesystem partitioning.
Take note this should be only declared for hosts with the format `iso` (or without the format) as mentioned from xref:../../project-specific-setup/declarative-host-management/index.adoc[Declarative host management].
They are declared in the `disko.nix` at the host root which they are then imported into `disko.devices` attribute.
Here's an example configuration for my desktop workstation.
[#lst:desktop-disko-config]
.`./hosts/ni/disko.nix`
[source, nix]
----
include::../../../../../hosts/ni/disko.nix[]
----
Take note the disko NixOS module already handles NixOS filesystem configuration (i.e., `fileSystems.<name>`) so if you have already have an existing hardware configuration, you have to delete it to prevent conflicting fstab configuration.
Another thing to take notice is disko is mostly intended for fresh systems.
Migrating your already existing systems with disko can be problematic.
In the <<lst:desktop-disko-config, previous config>>, the order of the declared partitions should match with the initial order when you manually partitioned the system.
If you cannot deal with it, reinstalling the system will help you there.