Path to YAML contact points configuration

Path to a file containing extra LubeLogger config options in the systemd EnvironmentFile format

Extra configuration to append to the default ~/.gitolite.rc

Path to YAML templates configuration

The keyfile which associates this machine with your tarsnap account

Environment file as defined in systemd.exec(5)

A list of capabilities to disable (for example, DHTV to say you cannot store DHT information).

An absolute file path (which should be outside the Nix-store) to a base64-encoded Ed25519 key for signing webhook payloads

Path to a JSON file to be merged with the settings

Environment file as defined in systemd.exec(5)

The environment hook will run before all other commands, and can be used to set up secrets, data, etc

Multiple GitHub Runners

Configures the rate limiting burst limit (number of messages per interval) that is applied to all messages generated on the system

Use services.mattermost.environmentFile to configure the database instead of writing the database URI to the Nix store

A path to a SSL secret key file in PEM format

Secret key used for signing

Password to connect to deluge server

Environment file as defined in systemd.exec(5)

The token from your Buildkite "Agents" page

Text content of the credential

Watchers to be included with the service alongside with their configuration

Environment file (see systemd.exec(5) "EnvironmentFile=" section for the syntax) which sets config options for mattermost (see the Mattermost documentation)

Path to CA bundle file (PEM/X509)

Additional packages or strings with context to add to the closure of the chroot

Fluent Bit configuration

File to load as environment file

If set, this file system will be mounted in the initial ramdisk

The passphrase the backups are encrypted with

Config files to merge into the settings defined in services.prometheus.alertmanager-ntfy.settings

The credentials to access the web interface, in case authentication is enabled, in the format username:hash

File to load as environment file

Whether to enable Validate configuration file.

The password for this entry

The directory to store the database files in

Use these credentials to authenticate during the HTTP upgrade request (Basic authorization type, USER:[PASS]).

Additional environment file or files as defined in systemd.exec(5)

Environment file as defined in systemd.exec(5)

A file containing the secret used to encrypt some rails data in a deterministic way in the DB

Store historical flow data in clickhouse

A unique identifier for this authentication token

Configuration for the rclone remote being used for backup

Additional environment variables to provide to authelia

Seconds to store cached auth entries for.

EnvironmentFile as defined in systemd.exec(5)

List of volumes to attach to this container

Amazon CloudWatch Agent configuration file

Connection string for accessing pgBouncer

Environment file as defined in systemd.exec(5)

Amazon CloudWatch Agent common configuration

Sets the password for WPA-PSK

Create the objectstore bucket if it does not exist.

Absolute path to a file with environment variables used for gitlab-runner registration with runner registration tokens

Environment file as defined in systemd.exec(5)

Absolute path to a file containing environment variables used for gitlab-runner registrations with runner authentication tokens

Datasource specific secure configuration

Sets allowed passwords for WPA3-SAE

Sets the password for WPA-PSK that will be converted to the pre-shared key

Sets the password for WPA3-SAE

Specifies the initial password for the user, i.e. the password assigned if the user does not already exist

Specifies the initial password for the user, i.e. the password assigned if the user does not already exist

If we can't use system-provided secure storage, should we proceed anyway?

.hg/store size (in MB) past which the nightly job generates clone bundles.

nix substituter to fetch debuginfo from

Should we bypass any attempt to use system-provided secure storage?