devenv-use...ig-validate(1)

πŸ“¦ version 2.4.0, in nixpkgs unstable

πŸ’… devenv-user-config-validate β€” the manual page, bestie edition

okay so real talk, the page you're reading is from the devenv-use...ig-validate(1) manual β€” that whole devenv-user-config-validate corner of the world. It's short, it's sweet, and it's literally just about checking that your user config file is valid. No cap. πŸŽ€


✨ NAME ✨

devenv-user-config-validate β€” validate the user configuration file. that's it, that's the job. πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

devenv user-config validate [--user-config] [--from]
[-o|--override-input] [-O|--option] [-j|--max-jobs] [-u|--cores]
[-s|--system] [-i|--impure] [--no-impure] [--offline] [--nix-option]
[--nix-debugger] [-c|--clean] [-P|--profile] [--reload] [--no-reload]
[--shell] [--eval-cache] [--no-eval-cache] [--refresh-eval-cache]
[--refresh-task-cache] [--secretspec-provider] [--secretspec-profile]
[--trace-to] [-v|--verbose] [-q|--quiet] [--tui] [--no-tui] [-h|--help]

🌸 DESCRIPTION 🌸

Validate the user configuration file. yes, that's the entire description. it's giving "confident and concise." the vibes are immaculate and the purpose is clear: it checks your user config and tells you if it's a slay or a mess. πŸ‘‘


πŸ’… OPTIONS πŸ’…

  • --user-config <USER_CONFIG> β€” use this user configuration file instead of the XDG default. main character file energy, fr fr.

🧚 INPUT OVERRIDES 🧚

  • --from <FROM> β€” source for devenv.nix.

can be either a filesystem path (with the path: prefix) or a flake input reference. lowkey flexible.

Examples:

--from github:cachix/devenv
--from github:cachix/devenv?dir=examples/simple
--from path:/absolute/path/to/project
--from path:./relative/path
  • -o, --override-input <NAME> <URI> β€” override inputs in devenv.yaml. you can just say "actually use this one" and it will. iconic.

Examples:

--override-input nixpkgs github:NixOS/nixpkgs/nixos-unstable
--override-input nixpkgs path:/path/to/local/nixpkgs
  • -O, --option <OPTION:TYPE> <VALUE> β€” override configuration options with typed values.

OPTION must include a type: <attribute>:<type>. supported types: string, int, float, bool, path, pkg, pkgs.

list types (pkgs) append to existing values by default. add a ! suffix to replace instead: pkgs!. the ! is doing so much work and honestly? respect.

Examples:

--option languages.rust.channel:string beta
--option services.postgres.enable:bool true
--option languages.python.version:string 3.10
--option packages:pkgs "ncdu git"       (appends to packages)
--option packages:pkgs! "ncdu git"      (replaces all packages)

πŸ”₯ NIX OPTIONS πŸ”₯

  • -j, --max-jobs <MAX_JOBS> β€” maximum number of Nix builds to run concurrently.

defaults to 1/4 of available CPU cores (minimum 1). not me rationing your cores like a snack.

  • -u, --cores <CORES> β€” number of CPU cores available to each build.

defaults to available cores divided by max-jobs (minimum 1). the math is mathing.

  • -s, --system <SYSTEM> β€” override the target system.

defaults to the host system (e.g. aarch64-darwin, x86_64-linux).

  • -i, --impure β€” relax the hermeticity of the environment. chaos mode (affectionate).
  • --no-impure β€” force a hermetic environment, overriding config. no chaos allowed, periodt.
  • --offline β€” disable substituters and consider all previously downloaded files up-to-date. airplane mode but make it Nix. ✈️
  • --nix-option <NAME> <VALUE> β€” pass additional options to nix commands.

these options are passed directly to Nix using the --option flag. see man nix.conf for the full list of available options.

Examples:

--nix-option sandbox false
--nix-option keep-outputs true
--nix-option system x86_64-darwin
  • --nix-debugger β€” enter the Nix debugger on failure. when things go wrong, you get to go in there yourself. detective era. πŸ”

🐚 SHELL OPTIONS 🐚

  • -c, --clean [<CLEAN>...] β€” ignore existing environment variables when entering the shell. pass a list of comma-separated environment variables to let through. like a bouncer with a guest list, honestly.
  • -P, --profile <PROFILES> β€” activate one or more profiles defined in devenv.nix.

profiles allow you to define different configurations that can be merged with your base configuration.

see https://devenv.sh/profiles for more information.

Examples:

--profile python-3.14
--profile backend --profile fast-startup
  • --reload β€” enable auto-reload when config files change (default). it just keeps up with you. 🫢
  • --no-reload β€” disable auto-reload when config files change.
  • --shell <SHELL_TYPE> β€” shell to use for interactive sessions (bash, zsh, fish, nu).

possible values:

  • bash
  • zsh
  • fish
  • nu

πŸŽ€ CACHE OPTIONS πŸŽ€

  • --eval-cache β€” enable caching of Nix evaluation results (default). work smarter, not harder.
  • --no-eval-cache β€” disable caching of Nix evaluation results.
  • --refresh-eval-cache β€” force a refresh of the Nix evaluation cache. out with the old.
  • --refresh-task-cache β€” force a refresh of the task cache.

πŸ™ˆ SECRETSPEC OPTIONS πŸ™ˆ

  • --secretspec-provider <SECRETSPEC_PROVIDER> β€” override the secretspec provider.
  • --secretspec-profile <SECRETSPEC_PROFILE> β€” override the secretspec profile.

⭐ TRACING OPTIONS ⭐

  • --trace-to <TRACE_TO> β€” enable tracing and set output destination(s). can be repeated for multiple outputs.

syntax: [format:]destination

Examples:

--trace-to stderr                              # json to stderr
--trace-to pretty:stderr                       # pretty format to stderr
--trace-to json:file:/tmp/trace.json           # JSON to file
--trace-to otlp-grpc                           # OTLP gRPC to default endpoint
--trace-to otlp-grpc:http://collector:4317     # OTLP gRPC to custom endpoint

multiple outputs:

--trace-to pretty:stderr --trace-to json:file:/tmp/t.json

destinations: stdout, stderr, file:<path>, http(s)://<host>:<port>. formats: json (default), pretty, full, otlp-grpc, otlp-http-protobuf, otlp-http-json.

when format is omitted, defaults to json. tracing is disabled by default. (yes, off by default β€” you have to ask for the lore.)

[env: DEVENV_TRACE_TO=] (comma-separated). [env: DEVENV_TRACE_DEFAULT_TO=] (comma-separated, used only when no explicit tracing is configured; set to empty string to suppress).


🌈 GLOBAL OPTIONS 🌈

  • -v, --verbose β€” enable additional debug logs. the girlies love a paper trail.
  • -q, --quiet β€” silence all logs. πŸ§˜β€β™€οΈ
  • --tui <TUI> β€” enable the interactive terminal interface (default when interactive).

possible values:

  • true
  • false
  • --no-tui β€” disable the interactive terminal interface.
  • -h, --help β€” print help (see a summary with -h). yes, the summary version is the trailer, the full one is the director's cut. πŸ’€

ok that's genuinely everything on the page β€” every flag, every default, every example, every env var. nothing skipped, nothing invented. you're so welcome. πŸ’–

🌸 and that's the whole manual, bestie! brought to you by validate (the source/version) and dated devenv-use...ig-validate(1) (the date, as these things go) β€” see you in the next --help. slay responsibly. 🫢✨

πŸ“¦ where this page comes from