devenv-processes-up(1)
πΈ 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 frafter: 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 bestieall: 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 overridesstrict_portsfromdevenv.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>β wheredevenv.nixcomes from. it can be a filesystem path (with thepath: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 indevenv.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: yourOPTIONmust 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--optionflag, and you can checkman nix.conffor 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 indevenv.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:bashzshfishnu
π 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:truefalse
--no-tuiβ disable the interactive terminal interface. no fancy UI, just vibes-h,--helpβ print help. and psst:-halone shows you a summary, the help text literally says "see a summary with '-h'" π
Heads up bestie:--offline,--no-eval-cache, and--no-reloadare 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
- nixpkgs unstable: devenv 2.4.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms