Filesystem ID, a generated uuid, its must be generated and set before attempting to start a cluster

Allow the cloud-init service to operate xfs filesystem.

Allow the cloud-init service to operate ext4 filesystem.

Whether to enable dsearch, a fast filesystem search service with fuzzy matching.

Directories from the host filesystem to be included in the sandbox.

Whether to enable the filesystem mount.

Allow the cloud-init service to operate btrfs filesystem.

Labels used to map jobs to their runtime environment

Fuse filesystem that returns symlinks to executables based on the PATH of the requesting process

Does all changes to the filesystem except destroy.

Type of the filesystem

The name of the Helm chart

The repo of the Helm chart

Whether to enable the autotier passthrough tiering filesystem.

The name of the Helm chart

The hash of the packaged Helm chart

The repo of the Helm chart

The hash of the packaged Helm chart

Whether to run services.transmission.settings.script-torrent-done-filename at torrent completion.

Filesystem type

Setup of xfs_quota projects

Determines where on the local filesystem a data node should store its blocks.

The contents to end up in the filesystem image.

The filesystem of the unencrypted device.

The version of the Helm chart

Whether to enable recvu feature which uses -u on the receiving end to keep the destination filesystem unmounted .

List of packages containing firmware files

The version of the Helm chart

Docker registry storage path for the filesystem storage backend

An absolute path to an executable to be run for each process killed

The directory where the secure filesystem will be stored in the rich execution environment (REE FS).

Attribute set of filesystem paths

Whether to enable emergency mode, which is an sulogin shell started on the console if mounting a filesystem fails

Shell code that will be run after all other hooks

The amount of filesystem space to not use for storage.

Backup the stdout of this program instead of filesystem paths

The path (inside the VM) to the device containing the root filesystem.

Whether the nix-channel command and state files are made available on the machine

Enable the cloud-init service

sysfs attributes to be set as soon as they become available

A whitelist of paths of git repositories, or directories containing repositories all of which would be published

Socket address

List of filesystem paths to archive.

This enables LXCFS, a FUSE filesystem for LXC

Use a tmpfs for the writable store instead of writing to the VM's own filesystem.

If enabled, the Nix store in the VM is made writable by layering an overlay filesystem on top of the host's Nix store

Filesystem location where Nexus should store the bank public keys.

Runs container in ephemeral mode with the empty root filesystem at boot

Local ZFS filesystem from which snapshots should be sent

Remote ZFS filesystem where snapshots should be sent.

Whether to compress firmware files

A list of paths to NNCP configuration files that should not be in the Nix store

Filesystem location where Nexus should store the subscriber private keys.

List containing JAR files or directories with JAR files which are libraries shared by the web applications

Storages are used to actually store your files

List containing WAR files or directories with WAR files which are web applications to be deployed on Tomcat

The filesystem directory to store blocks for the block store.

The filesystem directory to store your table store within.

List containing JAR files or directories with JAR files which are libraries shared by the web applications and the servlet container

Whether to enable S3 object storage as primary storage

An attributes set of directories that will be shared with the virtual machine using VirtFS (9P filesystem over VirtIO)

Whether the config should be checked at build time

Build and use a disk image for the Nix store, instead of accessing the host's one through 9p

Whether to install files to support the XDG Desktop Menu specification.

Whether to install files to support the XDG Icon Theme specification.

Whether to install files to support the XDG Shared MIME-info specification and the XDG MIME Applications specification.

List containing AAR files or directories with AAR files which are web services to be deployed on Axis2

Whether to install files to support the XDG Sound Theme specification.

Extra files to link and copy in to the initrd.

The location of the original password files

Path to a user's home directory from which to copy DankMaterialShell configuration files

The filesystem directory to store your protected store in.

Other initrd files to prepend to the final initrd we are building.

Where the tftp server files are stored.

The directory where Ombi stores its data files.

The directory where Plex stores its data files.

Deprecated directory containing client-writable configuration files

Realm files that the server is going to import during startup

Packages providing firewalld zones and other files

Path to the directory Traefik should watch for configuration files.

Directory for Apache's log files

The directory where Stash stores its files.

If set to true, Nix automatically detects files in the store that have identical contents, and replaces them with hard links to a single copy

List containing web application WAR files and/or directories containing web applications and configuration files for the virtual host.

Location where JBoss stores its temp files

The directory where Omnom stores its data files.

The directory in which to store BOINC's configuration and data files.

Directory for uploaded files

Directories to be scanned for further config files to include

The MODE determines which part of the NUT is to be started, and which configuration files must be modified

If set to true, you are free to add new users and groups to the system with the ordinary useradd and groupadd commands

AutoConfig files can be used to set and lock preferences that are not covered by the policies.json for Mac and Linux

Directory holding configuration and by default also incoming and temporary files

Data directory (-basedir) for SKS, where the database and all configuration files are located (e.g

Paths to SSL files

If set to false, the repo will be initialized with help files

The directory where deluge will create files.

The directory where Lidarr stores its data files.

The directory where Bazarr stores its data files.

The directory where SFTPGo stores its data files.