devenv-processes-up(1)

πŸ“¦
version 2.4.0 Β· 2 versions
, in nixpkgs unstable

🌸 NAME 🌸

devenv-processes-up β€” ok so the manual name is right there bestie, and the whole thing literally does one thing: start processes. That's the vibe. That's the assignment. πŸ’…


✨ SYNOPSIS ✨

devenv processes up [-d|--detach] [-m|--mode] [--strict-ports]
[--no-strict-ports] [--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] [PROCESSES]

πŸ¦‹ DESCRIPTION πŸ¦‹

Start processes.

That's it. That's the whole description. Iconic minimalism, no notes. 😭


πŸŽ€ OPTIONS πŸŽ€

  • -d, --detach β€” sends your processes to the background so you can get your terminal back. girlboss move 🫢
  • -m, --mode <MODE> [default: before] β€” the execution mode for process tasks. heads up: this actually affects dependency resolution, so it's not just a cute label. Possible values:
    • single: run only the task you named, zero dependencies, no plus-ones. main character energy fr
    • after: run the task you named and everything that runs after it (downstream tasks)
    • before: run all the dependency tasks first, then your task (upstream tasks) β€” this is the default bestie
    • all: your task plus its upstream and downstream tasks. the whole friend group shows up πŸ’€
  • --strict-ports β€” if a port is already taken, this errors out instead of auto-allocating the next available port. no port-sharing, we beefing πŸ₯Š
  • --no-strict-ports β€” turns strict port mode OFF, and it overrides strict_ports from devenv.yaml. yes it overrides your config, it said what it said
  • --user-config <USER_CONFIG> β€” use this user config file instead of the XDG default πŸ—‚οΈ
  • [PROCESSES] β€” name the specific process(es) you wanna start

πŸ”₯ INPUT OVERRIDES πŸ”₯

  • --from <FROM> β€” where devenv.nix comes from. it can be a filesystem path (with the path: prefix) or a flake input reference. so flexible, we love range πŸ’–

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. swapping the source like it's an outfit change πŸ‘—

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. and ngl the typing part is mandatory: your OPTION must include a type in the form <attribute>:<type>. supported types are: string, int, float, bool, path, pkg, pkgs.

list types (pkgs) append to the existing values by default β€” if you wanna replace instead, slap a ! suffix on it: pkgs!. periodt.

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> β€” max number of Nix builds running at the same time. defaults to 1/4 of your available CPU cores, minimum 1. so it's already being polite about your fans πŸŒ€
  • -u, --cores <CORES> β€” how many CPU cores each build gets. defaults to available cores divided by max-jobs, minimum 1. math. slay.
  • -s, --system <SYSTEM> β€” override the target system. defaults to the host system, e.g. aarch64-darwin, x86_64-linux. you can be someone else today ✨
  • -i, --impure β€” relax the hermeticity of the environment. letting a lil chaos in πŸ™ˆ
  • --no-impure β€” force a hermetic environment, overriding config. back in the clean room bestie 🧼
  • --offline β€” disables substituters and treats every previously downloaded file as already up-to-date. airplane mode but make it Nix ✈️
  • --nix-option <NAME> <VALUE> β€” pass extra options through to nix commands. these go straight to Nix via the --option flag, and you can check 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 β€” drops you into the Nix debugger on failure. when things go wrong we investigate, detective mode πŸ”

🐚 SHELL OPTIONS 🐚

  • -c, --clean [<CLEAN>...] β€” ignore your existing environment variables when entering the shell. pass a list of comma-separated env vars to let through β€” a VIP list basically 🎟️
  • -P, --profile <PROFILES> β€” activate one or more profiles defined in devenv.nix. profiles let you define different configs that merge with your base config. more info at https://devenv.sh/profiles πŸ’«

Examples:

--profile python-3.14
--profile backend --profile fast-startup
  • --reload β€” auto-reload when config files change. this is the default, it's already doing it 🫢
  • --no-reload β€” no auto-reload on config changes. changes require you to actually do something about it
  • --shell <SHELL_TYPE> β€” which 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 behaviour, already on, no notes ⭐
  • --no-eval-cache β€” disable caching of Nix evaluation results. starting fresh, we respect it
  • --refresh-eval-cache β€” force a refresh of the Nix evaluation cache. everything brand new again πŸ”„
  • --refresh-task-cache β€” force a refresh of the task cache. same energy, different 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 the output destination(s). can be repeated for multiple outputs, so yes, more than one is valid πŸ’…

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 the format is omitted, it defaults to json. Tracing is disabled by default, so nothing happens unless you ask for it.

[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. give me all the details πŸ”
  • -q, --quiet β€” silence all logs. peace and quiet, we're meditating 🧘
  • --tui <TUI> β€” enable the interactive terminal interface (default when interactive). Possible values:
    • true
    • false
  • --no-tui β€” disable the interactive terminal interface. no fancy UI, just vibes
  • -h, --help β€” print help. and psst: -h alone shows you a summary, the help text literally says "see a summary with '-h'" πŸ’–

Heads up bestie: --offline, --no-eval-cache, and --no-reload are all about turning things off that are normally on. nothing here is dangerous, but if you're confused why a thing feels stale or disconnected, check which of these you flipped. πŸ”₯

ok that's the whole page, every single flag accounted for, no skips, no summaries, we ate πŸ’…βœ¨ This little cutie comes from source up and it's filed under devenv-processes-up(1) in the manual β€” go forth and start some processes, bestie πŸ¦‹πŸ’œ

πŸ“¦ where this page comes from