nix/11.stylix
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

stylix: support multiple testbeds per module (#858)

Browse source 
Support multiple testbeds per module with
/modules/<MODULE>/testbeds/<TESTBED>.nix, while validating various
invariants.
This commit is contained in:
NAHO 2025-02-17 13:56:46 +01:00 • committed by GitHub
parent e86de61bb8
commit 211a8440e7
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
26 changed files with 52 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

0
docs/src/testbed-gnome-dark.png → docs/src/testbed-gnome-default-dark.png
View file

Side by side Swipe Overlay

Before

Width:  |  Height:  |  Size: 31 KiB

After

Width:  |  Height:  |  Size: 31 KiB

Before After
Before After

23
docs/src/testbeds.md
View file

@ -17,11 +17,10 @@ otherwise.
## Creation
New testbeds are defined by creating a file called `testbed.nix` within the
folder for the corresponding target. This file will automatically be loaded
as a NixOS module, with options such as `stylix.image` already defined.
The module should include any options necessary to install the target and
any supporting software - for example, a window manager.
Testbeds are defined at `/modules/«module»/testbeds/«testbed».nix` and are are
automatically loaded as a NixOS module with options such as `stylix.image`
already defined. The testbed should include any options necessary to install the
target and any supporting software - for example, a window manager.
If the target can only be used through Home Manager, you can write a
Home Manager module within the NixOS module using the following format:
@ -53,19 +52,19 @@ github:danth/stylix
└───x86_64-linux
├───docs: package 'stylix-book'
├───palette-generator: package 'palette-generator'
├───testbed-gnome-dark: package 'testbed-gnome-dark'
├───testbed-gnome-light: package 'testbed-gnome-light'
├───testbed-kde-dark: package 'testbed-kde-dark'
└───testbed-kde-light: package 'testbed-kde-light'
├───testbed-gnome-default-dark: package 'testbed-gnome-default-dark'
├───testbed-gnome-default-light: package 'testbed-gnome-default-light'
├───testbed-kde-default-dark: package 'testbed-kde-default-dark'
└───testbed-kde-default-light: package 'testbed-kde-default-light'
```
(This has been edited down to only the relevant parts.)
To start a testbed, each of which is named in the format
`testbed-«target»-«polarity»`, run the following command:
`testbed-«module»-«testbed»-«polarity»`, run the following command:
```console
user@host:~$ nix run .#testbed-«target»-«polarity»
user@host:~$ nix run .#testbed-«module»-«testbed»-«polarity»
```
Any package with a name not fitting the given format is not a testbed,
@ -75,7 +74,7 @@ Once the virtual machine starts, a window should open, similar to the screenshot
below. The contents of the virtual machine will vary depending on the target you
selected earlier.
![GDM login screen with a dark background color and showing a guest user](testbed-gnome-dark.png)
![GDM login screen with a dark background color and showing a guest user](testbed-gnome-default-dark.png)
If the testbed includes a login screen, the guest user should log in
automatically when selected. Depending on the software used, you may still be