DocsBlinkReferenceCommands and flags

Commands and flags

run, init, edit, and nuke, with every flag and its short form.

blink has four commands. run is the default, so blink on its own runs it.

blink run        # supervise the services in blink.yml with live reload (default)
blink init       # scan the project and write a new blink.yml
blink edit       # add, remove, or modify services in an existing config
blink nuke       # remove blink's state (.blink dir + logs) so the next run is clean
blink help       # command help

Supervises every enabled service in the config with live reload.

blink run -c blink.toml          # explicit config path (yml/yaml/toml/json)
blink run -s web,api             # only start a subset of services
blink run -u plain               # line-prefixed stdout instead of the TUI
blink run -u headless            # no UI at all (alias: -u none)
blink run -z                     # zen mode: native scrollback, no chrome
blink run -k off                 # don't kill processes bound to declared ports
blink run -l off                 # don't write per-service log files
FlagShortMeaning
--config-cconfig path, walks up from cwd when empty (also $BLINK_CONFIG)
--ui-ublink, plain, or headless (alias none)
--services-scomma-separated subset of services to start
--zen-zstart the TUI in zen mode
--force-shutdown-kon kills anything on declared ports before start, off never does (default on)
--logs-lon/off per-service log files at <log_dir>/<svc>.log (default on)

--force-shutdown and --logs take on or off. Any other value fails the run.

Scans the project and writes a new config from the services you pick.

blink init                       # writes blink.yml
blink init -c blink.toml         # writes TOML (extension picks the format)
blink init -f                    # overwrite an existing file
FlagShortMeaning
--config-cfile to create, extension picks the format (also $BLINK_CONFIG, default blink.yml)
--force-foverwrite an existing file

Reopens the picker over the services already in the config and writes back in the same format.

blink edit                       # edit the discovered config in place
blink edit -c blink.toml         # edit an explicit config path
FlagShortMeaning
--config-cconfig path, walks up from cwd when empty (also $BLINK_CONFIG)

Both init and edit open the same picker: space selects, edits a service, a adds one, f adds services from a sibling directory, p probes a service to discover the ports it binds, enter saves. Deselecting a service in edit sets disabled: true rather than deleting it.

Removes blink's state so the next run starts clean. Touches only project-scoped state by default and confirms first.

blink nuke                       # remove project state (.blink dir + logs), confirms first
blink nuke -y                    # skip the confirmation
blink nuke -g                    # also remove user-scoped ~/.blink (shared across projects)
FlagShortMeaning
--yes-yskip the confirmation prompt
--global-galso remove user-scoped state at ~/.blink, affecting every project